Add global server config + remove defaultconfigs feature

[SrRapero720]

this PR adds global serverconfig option which places server config files in CONFIGDIR instead of worlddir
also removes defaultconfigs because

1. nobody know how it works
2. nobody uses it
3. why? the only viable purpose is help modpackers to generate preferred default config files when these doesn't exist, but they already wrap generated config files, and the only reason to use that feature is for serverconfigs (and again, with the global server config option it has NO SENSE.

This was intended as a breaking change for 1.20.5+
is not humanly possible (without a lot of hackery) to keep compatibility.
Can be backported the global serverconfig doing a small check if file exists and if was a server config file to add manually the server.toml suffix and prevent duplicate filenames (if was even a problem) but is not something i will care about

[PaintNinja]

Postponed until after first 1.20.5 build to allow time for proper discussion and review

[Jonathing]

I know we want to save discussion for this PR until 1.20.5, but I'd like to say that at its current state, this PR is a no-go. This entire implementation hinges on a Forge config value of checking if we want to use global server configs or not. The defaultconfig system allowed the game to use a pre-existing config file to base its world off of instead of creating an entirely clean config file, which is rather essential for modpack developers.

In my opinion, what this PR needs to do is rework the defaultconfig system where if a config is found in the global path, it is applied to a newly-created world. If we want to keep the config value of forcing using server configs from then global path, that is fine, but it should be disabled by default due to the modulative nature of server configs in the first place.

[autoforge]

@SrRapero720, this pull request has conflicts, please resolve them for this PR to move forward.