Feat: Add release CI

[Totto16]

Add a release CI

This runs on every prerelease and release, and published the package automatically to npm, so we don't have to do that manually.

If it is a pre-release, it is published under the next tag, otherwise under the latest tag.

This was not tested as a whole yet (as it is not possible to test everything together that easily), but it should work, once
all TODO's are done. I tested every step of the pipeline separately locally, the pipeline was run nearly identical already on a test repo of mine (without npm publish)

Additionally I updated the normal Ci, to also use the newest Node LTS version and cleaned it up a bit.

Links

What is Provenance: https://docs.npmjs.com/generating-provenance-statements GH example for publishing packages: https://docs.github.com/de/actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages

TODO

• [ ] we need to have a repo secret NPM_TOKEN that can write to the npm registry and publish the package @JumpLink I think you are the only one, that can do that, you can follow this guide or ask me at any time on how to do that. We would need to create a NPM token, so you should create one on your own account, make sure to create a secret and not a variable as its hidden in all workflow logs and no-one can see it.

• [x] Use provenance workarounds, see https://github.com/yarnpkg/berry/issues/5430