Unhelpful warnings in Windows export profile

[KoBeWi]

Tested versions

4.5 dev1

System information

W10

Issue description

I noticed that when you export to Windows and put anything in version fields (File Version and Product Version, under Application category), you will very likely get these warnings:

File Version expects a number in format 0.0.0.0 (i.e. 4 numbers separated by period). The warning does not tell you that. It just says the version is wrong and you are supposed to figure out the correct format. Luckily there is a description for this property, which points to documentation page, except the Godot's version validator does not even respect it xd
According to that page, ProductVersion can take non-numeric characters (there is 5.00.RC2 as an example). I'm not sure if even the period format is enforced in any way by the OS, but seems like Godot converts all bits into int, removing all non-numerics. Also you can e.g. put 1.2 into version, which will be automatically converted to 1.2.0.0. You can export the exe and the version shows in details correctly. Despite that, the warning will still say the version is wrong.

Product Version is more interesting. You can put any string into it (even though the specification is the same as for FileVersion) and it does get written correctly and displays in exe details. However the editor still expects 0.0.0.0 format strings and will show the warning if you don't follow it.

Steps to reproduce

1. Create Windows export preset
2. Put anything in File Version or Product Version

Minimal reproduction project (MRP)

N/A

[B-Zhen]

I did some research and testing myself, and I can confirm that @KoBeWi appears to be correct that Windows does not actually appear to enforce any formatting on File Version / Product Version. However, RCEdit, which is the tool we use to modify these details does enforce some formatting.

RCEdit appears to have the following format requirements
File version - 0.0.0.0 format, as KoBe stated
Product version - Unlike what KoBe states, I could not input any string; it appears to accept any string that begins with a number. Aside from the number requirement at the start, it appears to allow everything else, it even allows special characters as shown below.

I'm not aware why we use RCEdit specifically or if we could potentially create our own fork of it to remove these restrictions. My basic suggestion is to allow users as much freedom as we can, since the OS itself has no enforcement, it would be interesting for any developers who want to hide easter eggs inside these fields. This would simply involve allowing users to do anything they want within the confines of RCEdit constraints.

I'll make a PR with the following changes

• Fixing the File Version warning to be more specific
• Fixing the Product Version warning to be more specific
• Editing the file warning logic to match the new "any string starting with a number" req