Improve user-friendliness of project version mismatch message

[aaronfranke]

Fixes #79095. EDIT: Updated the text to say "last edited" instead of "built", too lazy to re-take the screenshot.

Should be cherry-picked to 4.1, but it might be good to wait for translations to catch up?

Do not cherry-pick to 4.0, this code has changed between 4.0 and 4.1 to make space in the UI for labels.

[Listwon]

_project_feature_looks_like_version(const String &p_feature) is very error prone solution and workaround for something that should be changed in the core. Just move editor version to a separate config variable. It is not a "feature" so it shouldn't be stored as such in the first place. Look at the PR that you've rejected #59975

[akien-mga]

I tend to agree, it's not really a feature and we don't want it to be handled the same way as other features are handled - so that's a good case for a dedicated variable, which would also make it possibly more useful.

[aaronfranke]

The project version has a lot in common with the feature warning system. Both should result in the project manager warning the user about the project using something the current editor does not have. Having it be just another entry in this array also means the user can pin to a more specific version, like 4.1.1 or 4.1.1.stable.official, due to this I would argue against replacing the version entry in the features array because we would lose the ability to have multiple values. The only thing that needs to be different is the message we display to the user.

[akien-mga]

See godotengine/godot-proposals#7254, which this might address.

Edit: Not fully, this still doesn't make a distinction between an upgrade and a downgrade. I think we really out to make better use of the info we have to give users some actually useful messages - an upgrade from 4.0 to 4.1 is different from an upgrade from 3.x to 4.x, and a downgrade from 4.1 to 4.0 is also something else.

[akien-mga]

I'm not fully happy with the logic, I think it's a bit brittle and I don't like that we're reverse engineering metadata with heuristics when it's something that we wrote ourselves.

But that's a concern for improving this whole system further for a future 4.x release, for the immediate need to clarify the current warning in 4.1, this should do the trick.

[akien-mga]

Thanks!

[YuriSizov]

Cherry-picked for 4.1.1.