infra: #197/#240 create release using workflows

[thompson-tomo]

Avoids #197 and #240 being an issue going forward and resolves if maintainer steps below are done.

This introduces github workflow for managing releases. This workflow is triggered when a tag is added to a commit and performs the following:

• Set npm package version based on tag value
• Create npm package
• Uploads npm package to npm
• Create github release with npm package attached and auto generated release notes

Required steps by maintainers to enable closure of the 2 issues:

• Add 2.2.1 tag to commit bb82960 -> Needed for version mismatch between npmjs and github #240
• Setup trusted publishers https://docs.npmjs.com/trusted-publishers/
• Go to github tags and starting from 1.0.0 create a release for each tag by clicking the following option:

followed by the create release notes option:

-> Needed for #197

[thompson-tomo]

@PeterDaveHello / @AndrewSouthpaw / @thlorenz thoughts on automating the release process including release note generation?

Note the manual steps to generate old release notes described in description.