raidboss: DMU P5 initial triggers

[Legends0]

This PR adds triggers for P5 mechanics:

• Ultima Repeater AoEs
• Fell Forces Role Stacks
• Flood Start Location and Rotation
• Maddening Orchestra Triggers
• Celestriad Debuff and Tower Triggers, including initial tower direction, this is also configurable if strategy is CW or CCW from the vulnerable tower
• Catastrophic Choice In/Out Trigger
• Exaflare locations (Contains safe rows, but player may want to alter output to be shorter as it lasts 3.1s)
• Forsaken AoEs and Forsaken Bonds Stack with number

[Legends0]

I'm not sure how helpful the Exa trigger location can be. This mechanic may be too fast for the output to be meaningful and there may not be a predictable pattern to merge every other one. Also the output could remove NW/NE and instead use something like a number count as odds are always nw and evens are always ne. I guess ideally to make any actual use of it, the player would need to override the pattern matching with the markers they are using.

[Legends0]

Example outputs (this is with the P4/P5 ultima upsurge split) from the other PR #1117:
Tank:

Healer:

DPS:

[valarnin]

Is this another case where the heading is correct in the StartsUsingExtra line, and that could be used instead?

[Legends0]

When I check with raidemulator, the heading is valid in StartsUsingExtra, but the x,y cords are not.

    "matches": {
      "type": "263",
      "sourceId": "4001B0FD",
      "id": "C183",
      "x": "117.662",
      "y": "89.372",
      "z": "-0.015",
      "heading": "-0.785"
    },

In actorPositions 0.1s later:

  "4001B0FD": {
    "x": 103.5355,
    "y": 103.5355,
    "heading": -0.7855
  },

So while we can get the heading, I think we can't determine if it is the inner or outer part of the flood to be able to differentiate which pattern it is and thus the starting spot of two possibilities.

[Legends0]

I think the StartsUsingExtra is pulling data or can pull data from P4 positions.... since in this example the actor's name was Chaos and not Kefka.

[Legends0]

This might actually need to be changed to calling the two cardinal points rather than the intercardinal?

EDIT: Although I guess intercard is fine as that is the fastest point to interpret and get to the cardinal in next trigger...

[valarnin]

Same as above, was StartsUsingExtra checked for valid heading?

[Legends0]

This has the same issue as the early call, it too needs to have valid x,y coords and the StartsUsingExtra doesn't seem to have them in the log I looked at.

When I first wrote the Flood trigger, I assumed that maybe just the heading was necessary but I believe both are necessary as I found with more iterations that the heading can go either way in clockwise/counterclockwise and so heading can't determine clock. Additionally we need x,y because we can't start at an inner flood, the flood is there of course, so we need to look at the outer flood's location or know if we are working with an inner flood that the direction is flipped.

[Legends0]

Potentially here we should update the starting position to actually be +1 or -1 8dir over... I think the guides do that because kefkabin shows two possible starting positions at the inital flood, whereas here I've just been calling the middle point (the outer flood's intercard).

[Legends0]

I've updated this trigger to output the cardinal.

[Legends0]

ah, that comment is actually just wrong for Clockwise Example 2, I see it's just a copy of the x,y from previous line so will need to go back and check it.

EDIT 2: I see there is also another typo in Counterclockwise Example.