V4-planning: "MSI-style" version request

Hello,

Currently V3 API provides versioning according to [JEP 322](https://openjdk.java.net/jeps/322) (like `aa.bb.cc.dd+ee.ff`).
My updater sometimes encounters situations when only "MSI" style of version is available for local installations (like `AA.BB.CC.DD`).

If possible, I would like to have both version styles available in V4 API, like:
```
"version": { ... }, // the same block like in V3 assets
"msi_version": "11.0.9.101", // maybe for msi assets only?
```
_so that comparison logic could be controlled from within the Adoptium project, without having to change the updater._

I believe it should be possible to extract the necessary format from MSI packages / build process somehow and make it available in the API.

Also, currently my version comparison logic is a bit tricky because it tries to take different versioning schemes and workarounds into account. Implementing this would make comparison logic much simpler, straightforward and reliable.

**Related issues:**
https://github.com/AdoptOpenJDK/openjdk-build/issues/2248

Start by reviewing the V3 asset version block and related openjdk-build issue 2248, then determine how MSI versions are produced and where the V4 response schema is defined. Done means the source and format of msi_version are decided, its applicability to assets is clear, and the API output behavior is covered.

Written by the indexing model from the issue text.