Set up release process for VSCode plugin

[thatplguy]

It's important for each component in the toolchain to have an associated version number that is incremented on each release.

• Customers can check that they're using the latest version
• If they encounter an error, they can report the version they're using so we can reproduce it

Please design a release process for VSCode plugins that

• tags the GitHub commit in the main branch with the release version
• includes the release version in the VSCode plugin

Use whatever version naming scheme VSCode plugins typically use, likely semantic versioning with vX.Y.Z.

One option would be to have a CURRENT_VERSION file in the VSCode plugin folder and a shell script that

1. checks that the repo is clean
2. reads the version file
3. pushes a tag to github
4. bundles and publishes the VSCode plugin using the latest version

[podhrmic]

Please have a look at #57 and #62