Restructure config

[different-name]

• Use modules for enabling / disabling config elements, instead of imports
• Only import from top to bottom
• Introduce profiles for use cases (currently just server / desktop) instead of common/
  • This would allow for more than 2 use cases
  • The actual config files could be organised into only the subcategories instead, but with desktop/programs being graphical, or similar
  • This also means config files would not have to physically move when being switch between profiles, only the profile would be edited

[different-name]

Though a lot of files just change one option, and so it would be pretty pointless to create a wrapper option for that, in which case it would make more sense to just apply the option in the profile - which just means adding them all into one file, at least for the global file

Currently, this issue is solved by using the default files and grouping folders together to be bulk imported, meaning that only items in the extra folder are imported by themselves

I can't think of a good solution for this