fix: add missing release scripts

[derberg]

@ivangsa this is why release to marketplace did not work as it depends on a bump in package.json, that was missing a script

do you see any problem with us resetting versions of the plugin?

[ivangsa]

I think you are able reset the version numbering because it's a new and unique publisher-artifact-version but when we'll request the extension transfer in the marketplace, we (as in "the asyncapi publisher") are going to inherit a few version numbers that I think are going to clash with this new version numbering..

not sure how that is going to work..

[derberg]

@ivangsa ok, so to be in a safe position. I reverted to 0.3.3, and will add manually GitHub Release for 0.3.3 too. So this PR will release 0.3.4. Tbh I do not mind if we start with 0.1 or continue with 0.3, both make sense 🤷🏼

objections?

[asyncapi-bot]

🎉 This PR is included in version 0.1.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[derberg]

omg, I forgot to first create a GitHub Release.....lemme fix that...

[derberg]

@ivangsa hey, can you have a look at failing release https://github.com/asyncapi/vs-asyncapi-preview/runs/7110671016?check_suite_focus=true Was there a webpack config before refactor to react? I can't figure why it is failing

[ivangsa]

I will investigate further but npm run vscode:prepublish fails localy with the same error

[ivangsa]

@derberg It seems like some transitive depdencency was missing or with a wrong version...
this was the error/warning that gave me the hint

npm WARN [email protected] requires a peer of ajv@^8.8.2 but none is installed. You must install peer dependencies yourself.