Removed game settings overrides

[ferafiks]

PR Details

As discussed in #3272, removes the partially not working overrides from the game settings asset.

Breaking changes:

• Game.Settings.Configurations.Get<>() is now Game.Settings.GetConfiguration<>()

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[Ethereal77]

I've never used this feature. Do we have alternative for this?
I mean (correct me if I'm wrong) I've always imagined this was for scenarios like: I have a game with a specific configuration and graphics compositor, but for iOS and Android I want a specific configuration with smaller textures and a special compositor that disables shadows and post-FX.

If it is like that, it is an useful feature to have for multi-platform builds.

[ferafiks]

@Ethereal77 What you are describing wasn't possible previously, as the graphics compositor was not in a configuration, so it couldn't be overridden. The things you could override were mostly not related to hardware or platform (e.g. physics) except for graphics level, which from what xen mentioned in the linked PR, it probably wouldn't have worked. Also specific filters didn't work at all.

An alternative right now is to override the game class and add your own logic there (which is probably what you would have to do for most graphics-related settings). In the future, there could be a more proper way, like a replacement asset, but for now I'm just trying to remove this mostly broken feature