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

[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.

[KKhanhH]

I would suggest a template function for this templated on the StringToken, then you can specialize it in the textparser.cpp since it's only being used there anyway. To handle runtime to compiletime lookup, I would recommend doing a constexpr static lookup table like what we had for backgrounds2d table rather than a heap allocated map + std function, just do nullptr checks if you wanna leave some blank.

template <StringTokenType T>
void ParseStringToken(const Stringtoken& t);

using TextParserProc = auto (TextParser::*)(const StringToken&) -> void;
auto constexpr static textParserLUT = std::to_array<TextParserProc>({
 &TextParser::ParseStringToken<STT_LineBreak>,
 &TextParser::ParseStringToken<STT_CharacterNameStart>,
 nullptr, 
});

[PringlesGang]

Is this about what you meant? a35519b

[KKhanhH]

Yeah pretty much, i think you can use magic enum's enum containers too