Package binaries into VS Code extension

[AmazingPP]

I package all binaries into vsix in release workflow. This way we don't have to download the binary anymore, which brings the bloat of vsix, but it's tolerable.

The solution mentioned in #77 does not apply to VS Code extensions, because users do not download optional dependencies when installing extensions.

Also, I remove extension part checkForUpdates setting, since users can control extension (including binaries) updates using the extensions.autoCheckUpdates and extensions.autoUpdate settings in VS Code.

Closes #77.

[AmazingPP]

https://github.com/AmazingPP/zeek-language-server/releases/tag/prerelease

Here is a preview of the release workflow for review.

[bbannier]

I really like this. I was surprised that the vsix file containing all platforms is smaller than downloading a single uncompressed executable, but I guess that makes sense.

In the past I created the vsix file for upload to the vscode marketplace offline, but this new build process makes that impossible. Would you mind looking into what it takes to do this upload from CI? I can create needed tokens etc.

[AmazingPP]

I added Personal Access Token (PAT) check and publish setp into release workflow.

I did a simple test on the Publish command (it can be built and packaged successfully and request me to provide a token). Because I didn't have a token, I didn't completely test whether Publish is completely correct.