Enhancing the download experience

[ovflowd]

Enter your detailed suggestions:

Following the successful redesign of the main Downloads page as an all-in-one solution (#7037), we aim to maintain this momentum and further improve the Downloads page.

This effort includes enhancing the About > Previous Releases page by adding more details and a comprehensive list of versions. Additionally, we propose a simplified Downloads page that presents all available download options in a table format, similar to the previous version of the downloads page prior to the website redesign. This new page should be fully functional without the need for JavaScript.

Addresses part of the conversation from #7421

[ovflowd]

Both issues involve a similar subtask: updating our release generator to include a list of minor versions as a property of each release object. Currently, we only store major versions. This list can be represented as a tuple containing the version number and the release date as a UNIX timestamp.

For example:

{ "minorVersions": [["0.0", 1738424655], ["1.0", 1738424655]] }

Given a major version of { "version": "v23.0.0", "major": "v23.1.0" }, the corresponding minor versions could be represented as { "minorVersions": [["0.0", timestamp], ["1.0", timestamp]] }. Note that we only include the "minor.patch" information in the minor versions list.

This approach allows us to construct the string in the format of {major}.{minorVersion}, which saves space and eliminates the need to add the major prefix to each minor version in the list.