Run integration tests on an extension release

[divyenduz]

We run integration tests in the CI just before a release but there can be issues with an extension after the release, if

• the packaging had an issue
• it was released manually (i.e. no integration tests)

We can create a GH action that listens to changes in the extension version and runs integration tests (on all platforms #255) after an extension is released.

[carmenberndt]

We can create a GH action in case it was released manually. But if the packaging had an issue, the e2e tests will have to be added to the publish scirpt to get triggered.

[divyenduz]

Proposal: We can store last tested extension version in a file and run a GH action on schedule that checks that file vs the version actually published and if they do not match, we can run integration tests and on success, we can bump the version in this file.

P.S. We should add this, this would have caught these earlier:

#248
#279

[carmenberndt]

The code command can only be run in case VSCode is installed on the machine. The merged PR can not execute this command. I don't see a way to install VSCode in Mac, Windows and ubuntu from the CLI though.

[janpio]

Post publish testing moved to https://github.com/prisma/vscode-e2e-tests/issues/2