Access Token used has expired to publish new versions on VSCode marketplace

[Théo LUDWIG]

We can't release new versions as the access token has expired for the VSCode marketplace.

See: https://github.com/standard/vscode-standard/actions/runs/2747401022

[Pelle Wessman]

Right, so we need to do:

1. Preferably add more people to the VSCode Marketplace organization
2. Get a new VSCode marketplace personal access token for someone

On top of that it would be good to also do these while we're at it:

1. Verify our publisher through the standardjs.com domain
2. Lock down the HaaLeo/publish-vscode-extension to a specific hash, like currently 96a0a72. This to avoid a potential compromise of that repo to cause additional spreading through our repository.

[Feross Aboukhadijeh]

1. Who is best to add? @LinusU @Divlo?
2. Just got a new personal access token (they only last for 1 year) and added it into this repo.
3. I just added the TXT record for verifying the publisher and submitted the request. Once the VSCode team approves, it should be live.

[Théo LUDWIG]

Thanks @feross!
We can probably add @voxpelli, @LinusU and me @Divlo.
My email address is [e-mail].

@voxpelli email address should be [e-mail].

For v2.1.1 we can probably do a manual release, because the GitHub Actions already ran and published on open-vsx.
I'm up to do that, once I'm added to the standard organization on the VSCode marketplace. 👍

[Théo LUDWIG]

Fixed by 7167ab8.
The new release should be published both on Open VSX and the VSCode Marketplace.