Properly document historic dependency compatibility and feature set of the Windows toolchain

[stevapple]

Is your feature request related to a problem? Please describe

The Windows toolchain is evolving so fast that the compatibility status and features may change in each release. Currently Swift.org only documents the latest release, and the legacy part is incomplete.

Describe the solution you'd like

We should:

• state clearly that some information only applies to the latest version;
• hide unnecessary information according to user-selected toolchain version;
• check and complete the information table for historic releases.

The UI/UX can be achieved by a dynamic version selector (and route through hash history?), or let the generator to generate static pages for all releases.

Describe alternatives you've considered

We can continue to use a single page, but the page would be messy and hard to read.

Additional context

Linux toolchain dependencies and macOS version compatibility are also changing over time. If there's a way to handle it, we should also apply to other platforms.