[.github] workflow to handle creating a release whenever a `vX.Y.Z` tag is created

[djzager]

Similar to what we did here for container images being pushed to quay, when we see a tag of the vx.y.z form we should find the release associated with it and add the vscode extension package(s) to it as assets.

Pseudocode:

name: Publish extension package(s)

on:
  push:
    tags:
      - 'v*'

jobs:
  release:
    steps:
      - checkout code + setup node
      - update package.json version to match the tag (it should win now that we are setting it)
      - get the artifacts and rename them
      - find the release (because we are assuming it's creation is what made the semver compliant tag exist)
      - add artifacts to the release