Version precedence warning e.g. 1.81 -> 1.82 -> 1.9

Brief description of your issue

I submited an update to one of my apps using a perhaps old-fashioned versioning scheme, whereby, say, 1.9 is greater than 1.82. The update was accepted and published by winget. Now the latest version of the app that is being served is 1.82 rather than 1.9 (the numbers are an example). It would have been useful for a warning to be issued that I was submitting a version number that would be treated as lower than the last submitted package, in which case I would have changed the version number to 1.90. I suggest that some mechanism is needed to signal clearly the versioning scheme used by winget and to provide some checks.

Steps to reproduce

Submit two versions of an app using precedecnece 1.82 and 1.9.

Expected behavior

I'm not sure. Perhaps a warning that I was submitting a package that will not be considered to be the latest version by winget.

Actual behavior

There is no warning, the package is submitted and accepted, but it is not being served as the latest.

Environment

Irrelevant.

The issue does not name any files, tests, or entry points. Start by locating the version-precedence and package-submission validation paths in winget-pkgs, then determine where a lower-precedence version could be detected and how completion would be verified with a warning or check.