releaseAction

[ManuelHentschel]

What problem did you solve?
Fix #503. This PR updates the GitHub release action to automatically release the extension to GitHub and the marketplace when a tag matching v* is pushed.

How can I check this pull request?
This PR is kind of hard to check safely since the action is triggered automatically and produces a release to the marketplace, which can potentially affect all users of the extension. To be safe, I'd suggest keeping a .vsix file ready as backup when using the action for the first time.

For the action to publish to the marketlace, an access token is required, more details e.g. here.

[Ikuyadeu]

@ManuelHentschel Thank you for improving our releasing process. The changes look good to me.
To make security safety, I'll check the detail of secret tokens' access this weekend.

[ManuelHentschel]

While we're on it, we could also consider publishing a development build of the extension, similar to what Microsoft does with their GiHub Pull Requests:

• GitHub Pull Requests and Issues
• GitHub Pull Request Nightly Build

This would allow people that are interested in the extension to follow development closely without having to manually install from .vsix files all the time.

Setting this up should be rather easy, we'd just need to add a step that sets "preview": true, in the package.json and adds a note to the README.

Do you think people would be interested in this?

[Ikuyadeu]

OK, I set the secret, and I'll try it now.

[Ikuyadeu]

@ManuelHentschel Before using the new function of vscode, we need to fix the source code for the new vscode API.
Usually, I did that work before publishing, but I am working on #508 because it will be large fixing in this time.
I hope you will help me.