Fix the docs to reference latest version and make it a little easier to manage

[JackMeadDev]

The key intent here was to make sure the latest version was actually the one displayed in the docs, as I had an issue with this recently caused by confusion when we thought 1.0.0 was the latest version but discovered the arguments etc. all shown on the Readme were out of sync with that version. I then wanted to make it a little more sustainable rather than bumping this doc for every minor/patch release, so have suggested extending the action to automatically move the major version tag (e.g. V2) whenever a minor/patch is released, as per the suggestion in the docs so that future users can just ask for v2 and consistently receive the most up to date version despite no change to the current release process.

Happy to limit this to just the doc change (but tweaked to point to a specific minor version) if you'd rather not add the other section