Automate release of VSCode extension

[janpio]

Right now @timsuchanek has to manually ping @matthewmueller to execute a release of the VSCode extension. This is error prone and can be forgotten. We should automate that and integrate it into our release pipeline.

[divyenduz]

Internal notes:

• https://code.visualstudio.com/api/working-with-extensions/publishing-extension
• https://code.visualstudio.com/api/working-with-extensions/continuous-integration#automated-publishing
• https://code.visualstudio.com/api/working-with-extensions/testing-extension

Requested access to https://dev.azure.com/Prisma internally to be able to obtain a PAT (Personal access token)

[divyenduz]

Internal notes:

• PAT works (https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token) with "All accessible organization"
• There is no way to make PAT expiry more than a year, this will need manual renewal once a year VSTS PAT microsoft/azure-repos-vscode#327
• Tested a GH action workflow on the older extension feat(automate release) graphql/vscode-graphql#150

Next steps:

• Figure out where does this automation belong. Buildkite or GH action hook or something else?

[matthewmueller]

Wow, a 1-year expiry with no notification is a huge bummer. We should add this event to the company calendar or something.