docs: Replace static installation examples with generated information

[jhunkeler]

In the "Getting Started" documentation:

1. Use Github API to obtain the latest release object's assets
2. Generate installation commands for the various configs (e.g. py38, py39, py310, py311 for Linux and MacOS)
3. Publish

It might be useful to create a template and fill it in for each object (i.e each config gets its own page), and then generate a table on the "Getting Started" landing page. The user would be able to select targeted instructions for a platform/arch/python/release combination and go from there.

[zacharyburnett]

For now, I've added a version updater in #74. I will look into expanding into separate pages per-release, especially as the filenames and build instructions change.