Use minor version in EditorSettings file name

[KoBeWi]

When switching between different Godot minor versions, due to shifting defaults or changing shortcuts, there is a risk of losing data saved in editor settings. The most prominent case is the newest format change in 4.3, which causes the settings file to be "corrupted" in older versions, resulting in complete reset.

This PR adds a minor version to settings name, so now it's editor_settings-4.3.tres and so on. When opening new version for the first time, the editor will automatically search for older settings and migrate them.

Bugsquad edit:

• Fixes Editor settings wiped out when going from latest 4.3.dev to older releases #90846

[zaevi]

While it will migrate settings from older versions, the settings are independent for each minor version after the migration. If I change the editor settings in a new version (e.g., 4.4), the older (4.3) will still need to change again.

Is it possible to share the same editor_setting file for 4.3~4.x?

[KoBeWi]

Is it possible to share the same editor_setting file for 4.3~4.x?

It's possible, but I explained why it's better to not do that. Even before format change I had settings disappearing when downgrading and eventually I started running every version in self-contained mode. I don't see how it's desirable.

[zaevi]

Even before format change I had settings disappearing when downgrading

Not really, from 4.0 to 4.3.dev5, almost all editor settings are retained when downgrading, except for those newly added properties. That's why I want them to share the same one.

[KoBeWi]

4.2 -> 4.3 for example changed text_editor/completion/add_type_hints default, so if you go back to 4.2, you will have it disabled.
There is also the Duplicate Selected shortcut that changed 3 times already, so if you customize it to any former defaults, it will be gone.
Make Unique Sub-resources shortcut has no default, but it used to be bugged, so if you set it and go back to a bugged version, it will be gone.
There are more examples of random things like that and when you move between versions you will only discover that something is wrong when you try to use a functionality and notice that it behaves differently than you customized it.

[akien-mga]

Looks good to me.

I agree with this approach, we've had a few issues due to reusing the same file across minor releases, and this will grow as the 4.x series keeps getting more and more features.

[akien-mga]

Thanks!