How to document distinct latest version for extended release cycles

[captn3m0]

We currently track separate EOL dates for extended support. In many cases, the extended support releases are gated, or provided elsewhere, and as a result - have a distinct "latest" version number.

Examples are:

• Quarkus, where extended = distinct builds for RHBQ
• Qt, where we only track OSS releases, but extended releases are for commercial support.

This was somewhat accounted for in the releases.json draft, with each distinct "variant" coming with its own latest version. But I'm unsure of how to track this best under our current schema, both for the API and the website.

The reason I'd like to track this is to ensure that users on extendedSupport should not be able to rely on the latest version information (if available), and get accurate alerts (current installed version != latest). As it stands, our tooling does not really support extended version matches.