Consider using gh actions to publish extensions

[a5ehren]

Your process at the moment seems to require manual publishing to OpenVSX and the MS VSC Marketplace, which isn't ideal. If you put your secrets in the vault, there are GH Actions to do this at the same time as you do your npm publish. I use them in my project and it works great.

      - name: Publish to Open VSX Registry
        uses: HaaLeo/publish-vscode-extension@v2
        id: publishToOpenVSX
        with:
          pat: ${{ secrets.OPEN_VSX_TOKEN }}

      - name: Publish to Visual Studio Marketplace
        uses: HaaLeo/publish-vscode-extension@v2
        with:
          pat: ${{ secrets.VS_MARKETPLACE_TOKEN }}
          extensionFile: ${{ steps.publishToOpenVSX.outputs.vsixPath }}
          registryUrl: https://marketplace.visualstudio.com
          

I'd send a PR, but I don't have your tokens so it would be kinda pointless.