Dialoguepage trifurcation

[PringlesGang]

Trifurcates the DialoguePage class into separate instances for dialogue, backlog entries, and tip entries

Moves text parsing to a separate class, with separate directive functions for dialogue, backlog, and tips, handling what is parsed and how

• Fixes [DialoguePage Refactor Step 3] Duplicate string parsing for the backlogs so that they don't keep the "styling" from the main DialoguePage #249
• Only pushes a new backlog entry at the end of InstMesMain, instead of at the start of InstMes
• Fixes Fix JP word-wrapping #283
• Give dialogue boxes and nametags more freedom in how they can be rendered
• Implement placing the dialogue box through ScrWork
• Fine-tune nametag visibility and positioning
• Allow for text to be transformed during rendering
• Perfect nametag and ruby positioning during parsing
• Fix up chlcc/cclcc backlog entry rendering and formatting
• Implement InstSetMesModeFormat and make the parser use these values
• Fix DialoguePage clearing semantics
• Allow for text centering for backlog entries
• Add support for EN wordwrapping for added glyphs
• Clean up profile
• Add profile endpoints for InstSetMesModeFormat values
• Implement Erin textbox fading
• Disable cursor requests when hovering a scrollwheel area

Test English wordwrapping with https://github.com/CommitteeOfZero/impacto-patch/pull/1

English TextModesInfo config is very negotiable

[KKhanhH]

Instead of having a backlogpage pointer per backlog entry (which adds a lot of indirection and fragmentation), could we instead maybe store a vector of backlogpages inside backlog menu (since it's not polymorphic), and then access that in backlogentry with an index and maybe a pointer to the backlogmenu?
If backlog max count should be a bounded value, we should store it in a static array as well.

[PringlesGang]

Yeah that's definitely a good idea. I'm already working on a commit to fix this, which would also simultaneously add a cap on the number of backlog entries (because right now it'll just keep appending indefinitely), but it's growing kinda large and out of scope for this PR. Mind if I fix this in a later PR?

[Enorovan]

Review feedbacks, some may be addressed elsewhere :

• You can still open empty backlog in C;HLCC.
• Double linebreaks aren't parsed in Tips Menus.
• Weird case when skipping on "looped" lines in Map Trigger.
• Weird Cursor Pointer in C;CLCC Tips Menu.
• Erin Box is supposed to fade-in/fade-out.

[PringlesGang]

Review feedbacks, some may be addressed elsewhere :

• You can still open empty backlog in C;HLCC.
• Double linebreaks aren't parsed in Tips Menus.
• Weird case when skipping on "looped" lines in Map Trigger.
• Weird Cursor Pointer in C;CLCC Tips Menu.
• Erin Box is supposed to fade-in/fade-out.

All should be fixed now, except for being able to open an empty backlog in C;HLCC. On PS3 this is also possible though, so I don't think that was an issue in the first place