Implement per-game configuration, refactor configurations in general

[kiwidoggie]

This should solve the issues of:

#564

and

#397

And prepare the work for:

#614

[kiwidoggie]

Can I get comments on this?

I did some profiling, at most it's negligible perf impact, could be less if we moved out the log settings to be on-game-start. Logging in general kills perf more than the settings does.

1. The idea here is instead of having fragmented configuration block, then manually reading/writing each load/save, to just keep around the toml config file which gives us a few benefits
2. Can check existing config against the current defaults to see if it's been changed (and need to load/re-save for new options)
3. It allows to have default fallbacks in the event that a value isn't found in loaded config (this allows upgrading seamlessly)
4. Changes are wrote directly to the toml object and can be saved at any point without keeping everything manually synced
5. Fixes an issue where values aren't exposed properly, or not matching the config value

Allows you to save via title id, where "config" is the default TID, but you could save it as per-game, then upon loading switch the config managers title id, and it will automatically use those settings, seamlessly without modifying the existing codebase

I currently have helper/passthrough functions to allow shad to build without too much modifications but those should be deprecated for something more direct

If perf is super a concern I can make something that just passes around a global config block (memory structure) instead of going to/from toml, but I think it defeats the purpose of having the nicer config setup.

[kiwidoggie]

Bump, I'd like to complete this and move on to other feature requests.

[Hermiten]

It's marked as a draft

[kiwidoggie]

Yes, I'm aware that it's marked as draft. It's because it involves major code breaks. I wanted to ensure that the developers are okay with the method I am going to be doing things, before committing to writing a bunch of code that's not going to be used because it was not what the developers wanted. That's why I was looking for input.