raidboss: r12s initial p2 triggers and timeline

[Legends0]

These I have been working on.

• Includes strategy support for both DN and Banana Codex.

Timeline is based on network log.

Some of ideas of things TODO:

• Replication 1 has an edge case which in theory should never be hit, I also never really paid attention to its output cause I just never modified it to my position needed so my calls were always both intercard locations which seemed correct. It kind of feels late to call, but I don't see how else it can be called sooner other than possibly a heading-based prediction, for which the data may not arrive in a timely manner as well.
• Double Sobat in P2 can have some weird output if the targetted player quickly changes or quickly moves to a new direction prior to the snapshot but most cases it is accurate. Not sure if this is fixed with using the target's location compared to boss center in the match instead of boss heading.
• Replication 2 Nukemaru (JP Strat) config/detection. While I can probably code up something basic for it, I likely won't be able to test this but it has been added.
• Tower locations in P2 (I couldn't see a way to collect their location until after the fact when players have debuffs). It would also be helpful to know where that pesky earth tower is, which maybe is in its startsUsing cast that I just never bothered to check. The call outs in general here could be kind of spammy with the Doom (for cleansers), Pyretic, and avoid earth. EDIT: The Combatant Memory lines for them being added prior to casts has unique BNpcID for each tower type.
• Replication 4 breakout outputs based on dn strategy (call the group 1-4/intercard quadrant and to grab stack or defamation?) . EDIT: NA/EU/JP all do this differently, so probably going to end up with multiple config options here to eventually.
• Final AoE set could probably be adjusted as right now they are both alert bigAoes. I haven't actually looked into the damage it does, I think the damage goes up with each cast as there are more actors casting, but I never noticed an issue here.
• Fix replication 2 reenactment 1 in timeline, currently it is coded for DN strategy.

Note: Didn't realize renaming branch would close previous PR #964 and didn't have permissions to re-open the PR.

[Legends0]

The strategy detection for replication 2 does not use the location of the abilities. This creates an issue when strategies used are the flip of a matched strategy, such as Banana Codex being West oriented and the Nukemaru strategy being East oriented. The direction calls will be incorrect in Nukemaru. While a user could override the output here to correct for the flipped strategies, it may be beneficial to sort the order such that order[0] is always north and order[1] always south instead of comparing both in the current design that assumes log lines for the pairs north/south, ne/sw, e/w, and se/nw could be in random order.

[Legends0]

The strategy detection for replication 2 does not use the location of the abilities. This creates an issue when strategies used are the flip of a matched strategy, such as Banana Codex being West oriented and the Nukemaru strategy being East oriented. The direction calls will be incorrect in Nukemaru. While a user could override the output here to correct for the flipped strategies, it may be beneficial to sort the order such that order[0] is always north and order[1] always south instead of comparing both in the current design that assumes log lines for the pairs north/south, ne/sw, e/w, and se/nw could be in random order.

Upon further review, I realized I did retrieve in an order and then store it with order = [0, 4, 1, 5, 2, 6, 3, 7] where these represent the dirNums of each ability. This probably could use a map so that retrieving items in replication2AbilityOrder could be better understood like order[north]/order[south] instead of the order[0]/order[1].

[Legends0]

I'll get to adding more of the nukemaru related calls for R12S Replication 2 Locked Tether later.