Basically, run the update-versions script and commit the results into the repository.

The way this used to work is that the script would be run as part of the deployment process, so the generated information didn't live in the repository and existed only in the docs. I'm proposing we change that because:

1. I generally prefer "what you see is what you get"
2. While we could write a custom workflow to deploy the site to github pages, it would be a bit complicated. It seems simpler to fold these updates into the workflows that push new documentation to this repository.

As part of this, I made some modifications to the update-versions script so it'll run if the repository already has a latest symlink and version information.

This is part of #1