Enhancement: Unify system of key names across the settings

[antirotor]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

We are using multiple types of key names across the settings, from CamelCase, snake_case to just strings with spaces inside. This is all fine and good until we hit the case where we'll need to serialize those keys in format that doesn't support it or use it as class attributes, etc. Fine example is this PR that is trying to unify one part of the settings to arbitrary strings: #6000

How would you imagine the implementation of the feature?

We should pick one system and stick to it.

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

[cuID:OP-7544]