Make it possible/easy for users to switch to different versions of the ESCET website

The problem

Currently, our standard visible website is at https://eclipse.dev/escet. Version-specific websites are at, e.g., https://eclipse.dev/escet/v0.7. There are no links from the standard visible website to the version-specific websites, so users are likely unaware of them.

Proposed solution

The first solution will consist of:

• The list of versions is stored in a file:
  • This file will be updated whenever a new release is done, or when an older website (M/RC version) is removed.
  • This updating will be integrated into the website manipulation scripts.
  • Web pages will load the file through JavaScript, and update the page dynamically, such that we don't have to regenerate old websites once the list changes.
• Add a page https://eclips.dev/escet/versions.html that contains links to the various website versions. It will take you to the root page of that version (no deeper linking).
• For the fixed website pages:
  • Allow switching to some of the more recent versions (at least latest release, milestone, RC and nightly), or go the page with all versions.
  • The full list is already long and will only grow, so limiting the list that is shown seems like a good idea.
  • We have only 12 fixed website pages, and they have been quite stable so far, so this should be easy to do.
  • Only new website versions will get this new feature. Old versions won't get it, so we won't change already deployed websites.
  • The links will be to the root of the other website versions, as the first websites (v0.1 - v0.3) didn't have the current fixed pages to allow for deeper linking. So, from the current CIF website, going to a nightly will take you to the ESCET home page of the nightly website.
• Add a link to the 'versions page' on the download page.

Possible things to be considered later:

• Deeper linking when switching to a different website version, for newer releases that have the same pages as the current pages. This requires knowledge of what pages there are for which version. Also, the 'other' versions can change over time. One solution could be to query live whether the deeper pages exist or not, making it dynamic and always up-to-date.
• Version switching from AsciiDoc-generated webpages.