Redesign products and legacyurlmapping configuration to be driven by versions.yml

[Mpdreamz]

Now that we have versions.yml we should ensure our other configurations are driven by it.

Product list

• Can we encode this list in versions.yml or a new products.yml ?
• Ensure each product is attached to a single versioning system?

products:
  elasicsearch:
    display: 'Elasticsearch'
    version_scheme: 'stack'
 
versioning_systems:
  stack: &stack
    base: 9.0
    current: 9.1.0

We can then also expose display as a variable e.g {{ product.elasticsearch }} or maybe even {{ .elasticsearch }} as special syntax?

Legacy Url Mappings

Ensure each mapping maps to a versioning scheme that way we can:

1. Automatically inject the base Major.Minor+ (or Major.x+) in the version dropdown based on the base of the versioning scheme.

2. display the latest version of the page.
   We either display:

   • the listed products and their latest version
   • the latest version according to the legacy_mapping versioning scheme.

[cotti]

Moved to Needs Input: Waiting on final feedback