Move 'Supported Versions' release table from docs to website for automatic generation

[stockholmux]

Is your feature request related to a problem? Please describe.

Today, in the documentation, there is a table that lists all the supported versions:

https://valkey.io/topics/releases/#list-of-supported-versions

This page is manually maintained from valkey-io/valkey-doc . Valkey 8.1 was released on March 31 and we missed adding 8.1 to this table for 70+ days. Manual updating is tedious and easy-to-miss but the supported versions is a very critical piece of information that, if not maintained accurately, could lead to users not adopting the most-up-to-date version.

Describe the solution you'd like

Move the supported verisons table to the website and generate the content with the YAML files in valkey-io/valkey-io.github.io/content/download/releases. These already have to be updated as part of the release process and this would reduce a manual step in releases.

Describe alternatives you've considered

We could add a line to the release process to update valkey-doc.

Additional context

n/a

[zuiderkwast]

We could update this table ahead of time, to include the planned versions 9.0, 9.1, 10.0, 10.1. Then we don't need to update it all the time. We can't put in an exact date obviously but we can put in year and month probably.