feat: global configuration system

[Krzyhau]

These informations should be save somewhere in a common file for HAT to determine how to handle mods:

• enabled state of the mod (whether the mod should load or not)
• mod version to load (by default, loads the newest one)
• custom ordering of mods (a secondary, after dependency priority, user-based ordering for resolving asset conflicts)

[Jenna1337]

Related: #3

[Krzyhau]

I've implemented a very basic solution that should be sufficient enough: blacklist.txt (16c45eb) and prioritylist.txt (f33d767) files within the Mods directory, in which you can list files to disable and prioritize during mod loading process.

More advanced configuration should be implemented in an individual mod configuration system, for which I've created a separate issue: #18

As for this issue, I'm considering it done.

[Jenna1337]

I heard the term "blacklist" is a term that should be avoided because it could be considered racist or something. Consider changing it to "blocklist" or "ignorelist" or similar

[Krzyhau]

The term "blacklist" does not refer to human race in any way. However, I might change it to ignorelist just because it sounds better when paired with prioritylist.

On an unrelated note: