[Feature]: Loosen constraints on UVTT import

[kwvanderlinde]

Describe the Problem

When importing a UVTT file, MT first does a strict check that the "format" is set to "0.2" or "0.3". While this works for UVTT files crerated by current versions of DungeonDraft, other software does not necessarily set the format to one of these values. One example is Arkenforge which sets it to "1.0" despite following the 0.3 format. As a result, users are not able to import UVTT files from Arkenforge without first manually editing the UVTT file.

Looking to the future, we can expect a time when DungeonDraft will bump the UVTT format to something higher than 0.3. When that happens, current versions of MT will not be able to load these new UVTT files, even if the structure is essentially the same.

The Solution you'd like

I'd like us to soften the format check on UVTT imports. If the format number is not one we recognized, we would show a warning to the user explaining that the file may not import correctly. The user would be allowed to continue with the import or cancel the import.

If the user continues with the import, we would try to import the UVTT as best as we can, assuming the same structure as the latest format supported by MT (i.e., 0.3). Any unknown fields would be ignored. Known fields would be interpreted liberally if possible. Fields that can have reasonable defaults will not be required even if they ought to exist.

Alternatives that you've considered.

Getting all third parties onboard with a proper UVTT spec that can be relied on.

Additional Context

No response

[bubblobill]

If we go with warnings, we should filter for known variations.
Parse Arkenforge 1.0 as 0.3, etc.
Provided Arkenforge 1.0 does not extend UVTT 0.3 with their own fruit.