use rich_print when in-editor

[ZackeryRSmith]

Allows for a much cleaner separation of the logs. This PR introduces scaffolding for the options profile. Similar to how hint_color currently is. Works towards #450

BEFORE	AFTER

[ZackeryRSmith]

As for using the options profile scaffolds. If ModLoaderStore is nil, which in most cases it isn't, we could just use fallback colors.

Alternatively, ModLoaderStore logs get to be bland and colorless. I'm reaching for this option, as these logs are very minimal (literately just a single line) and at the top.

Scratch all that, just now seeing _configure_logger

[ZackeryRSmith]

OLD	NEW

[KANAjetzt]

Two things:

• Do we want DEBUG to be bold as well?
• In the editor, we can remove the ERROR prefix.

[ZackeryRSmith]

Do we want DEBUG to be bold as well?

I'm going to argue, no. Debug logs are, well debug. Color and boldness draws attention. It's common practice to reserve color for status', warnings, or errors. Giving debug logs a color elevates them visually to the same importance, which for me breaks the mental model. Where you can just filter the logs for your mods debug messages, I find personally that keeping debug unbold is the way to go. For reference this is what bold debugs look like

Original colored log screenshot in this PR

In the editor, we can remove the ERROR prefix.

Never noticed that, but you're right, let me make that change

[KANAjetzt]

Fair point. I think there is still enough separation between the log types with the color alone, and the bold prefix ties all the Mod Loader logs together.

Adding a bold toggle in the options for each log type might be a bit excessive, but maybe just one for debug?

[ZackeryRSmith]

Agree with you there. Let's make bold the default option for debug logs with an optional toggle. I'll make the changes once I get home

[KANAjetzt]

Only some small nitpicks, looks very nice, ty👍

[ZackeryRSmith]

I'll write a follow up PR which addresses the suggested changes