Release process for kdb VS Code extension

On each push to the main or dev branches` a VSIX file is built and uploaded to Downloads Portal

Steps for creating a new release

Update the package.json to bump the version for the extension. This is important because when installing the package (VSIX), it's important to have the updated version to ensure VSCode does not install another version. This uses semantic version of build.release.patch (e.g., 0.1.8)
Update the CHANGELOG.md to include the release version the the appropriate comments on updates. This uses semantic version of build.release.patch (e.g., v0.1.8)
Merge the changes
Create a tag on main locally, then push it to remote.
```
git tag v1.0.0
git push origin v1.0.0
```