Translation branch code cleanup

This is purely a bunch of code quality improvements and maintenance optimizations to fix some of the issues I had with the code, particularly with the additions on our side, and doesn't contain any new content.

I've made the following adjustments:

• All hardcoded color calls to other dialogue have been replaced with CHARA_TEXT or SET_KOJO_COLOR to guarantee correct functioning with alternate dialogues
• CHARA_TEXT now supports str, strl, and strw parameters, which call the PRINT_STR(L|W) functions with the relevant character's color
• Duplicate lines with only minor differences for Reisen's fallen state in Tewi's dialogue have been simplified and trimmed down
• TRYCALL is used any time a function is used from another dialogue
• Some functions have been moved out of KOJO and into the main space to allow them to be easily reused in other dialogues (@QUAKE, @K41_FIRSTKISS, @K41_PUSHDOWN, @K97_RUNOFF)
• Fixed some misnamed functions in KOJO that used the id of other characters
• Fixed some commands that would set the wrong text color
• Double Handjob dialogue for Tewi has been pulled out of COM80 dialogue and into new custom SCOM (will be part of a dev branch MR)

This significantly decouples the various dialogues from each other. It doesn't deal with inline #FUNCTION functions, yet, for which I'll probably have to think of a good solution, but it's a good step in the right direction.

I also want to make the following recommendations for dialogue development:

• All dialogues should be considered as separate modules, and it should be possible to add or remove any at will
• Dialogue for other characters should always be colored through CHARA_TEXT or SET_KOJO_COLOR
• Since alternate dialogues are possible, dialogues should not assume that any particular dialogue is active. If absolutely necessary, the active dialogue can be checked through its name or index (though the index should only be used in #FUNCTIONs as they cannot check the name)
• Dialogues should not call functions from other dialogues unless absolutely necessary. If a function is generic and can be reused, it should be promoted to a general function and moved out of KOJO
• Non-KOJO functions should try to avoid calling KOJO functions directly, if necessary, they should always be called through a TRYCALL

This should help prevent potential issues in the future, especially if alternate dialogues are introduced.

Note: Due to removing the now redundant K60_PARSEE_X_ZONE, the dev branch will have an error since there was one more usage there in Add_HashihimeServices.ERB (Line 285). That line can be replaced with RUNOFF(60, 0).