Proposal: Implement breaking changes for 8.0

[valarnin]

There are a lot of TODO items and things that have been sitting around for a while waiting to be cleaned up (e.g. normalizing styling of function names and properties).

Should we declare that 8.0 will clean up these outstanding TODO items and user JS written against older styling might break?

Similarly, there are some parts of OverlayPlugin that I would like to clean up or change prior to 8.0 that may also cause breaking changes.

[xiashtra]

In general, I think it makes sense to both expect and implement breaking changes at expansion boundaries.

We could make a branch to start testing/merging those changes into, and have it ready to cut over when the time comes.

[xiashtra]

I think we can use this issue to collect a list of things we'd like to do for 8.0.

#943 (comment)

Trigger logic has grown organically and it no longer makes sense fully, and we should maybe think about updating things before 8.0

[xiashtra]

#925 (comment)

One of the "breaking changes" I want to look at implementing is a requirement that Outputs entries have a corresponding Responses entry. As in something like this:

[xiashtra]

#919 (comment)

Kind of wish we were always more explicit with naming ID fields everywhere (e.g., abilityId, sourceId, etc.) to help avoid errors like this.

That's on my list of things to clean up, but it'll be a "breaking change" because all encounters already loaded into raidemulator will no longer be valid.

[xiashtra]

#869 (comment)

We might want to update those for consistency.

I think that sort of change could break user triggers if they're reliant on Outputs, so we should be careful. Maybe put that as a TODO list item for end-of-expansion-content cleanup?

[Jaehyuk-Lee]

#947

Rename TimelineReplacement

TimelineReplacement was originally used for translating timeline. But now its role has been expanded to translate the NetRegex triggers' source, including raidboss and oopsyradisy ones.

proposal: TranslationReplacement

more opinions: I don't think this is an ideal name, so please leave any comments for a better name.

Also, there are some more variable names similar to TimelineReplacement. I think those ones should be renamed for consistency.
(e.g.timelineReplace, getTimelineReplacement, etc.)