feat: ✨ ML Options: Add the groundwork for loading custom options

[ithinkandicode]

Adds the ability to manage various ModLoader options through Godot's own GUI.

I've set this up so that you can quickly change the options profile you want to use. There's a file called options_current.tres, which determines the options resource that's currently being used. I've provided a few other profiles too.

I've put all the options stuff in its own directory as there's quite a few files.

Todo

• So far I've only integrated the enable_mods option, as I want to get feedback from you guys before this proceeds further. So the other options still need to be integrated. But that would be better in a subsequent PR, so that this one remains focused on just adding the groundwork.
• I also haven't set this up with the auto install scripts, if someone else could handle that I'd appreciate it greatly as I haven't really worked on that part of the code!

Notes

Docs: https://github.com/GodotModding/godot-mod-loader/wiki/Upcoming-Features#options

Related:

• Store certain local variables in a dictionary (detailed notes) #146

[Qubus0]

Neat and definitely more user friendly than all the flags. We might want to integrate the flags with the options system though - parse them in the ModLoader _init and only use them later. Flags should override the options though.

I don't think we need all of those examples, the options are pretty self-explanatory, especially if we use export hints like this for dictionaries export(String, DIR) var path_to_mods (see: https://docs.godotengine.org/en/stable/tutorials/scripting/gdscript/gdscript_exports.html)

[ithinkandicode]

@Qubus0 The examples aren't to help people understand the options, they're for quickly applying options without affecting your current settings:

• current = Your current settings, can be anything
• default = Reset to default without affecting current settings
• disable_mods = Quickly disable all mods
• production*_ = Deploy for distribution (workshop and non-workshop versions, depending on the game)

So they basically act like profiles. That's why options_current.tres exists, since otherwise all your options would be stored in a single resource, with no way to quickly change option profiles.

I guess it was the being called options_examples that was confusing? I've renamed it to options_profiles

[ithinkandicode]

@Qubus0 Turns out that renaming them to profiles works so much better! Thanks for the feedback

[ithinkandicode]

We might want to integrate the flags with the options system - @Qubus0

See #146 for discussion on things like that, this is just the initial groundwork :)

[Qubus0]

Cool stuff, small remarks, overall approved!

[ithinkandicode]

All review issues have been resolved, thanks for the review @Qubus0 :)