ci: workflow to autogen a changelog and publish to npm

[iloveitaly]

works for me on: https://github.com/iloveitaly/better-node-inspect

[Mr0grog]

Adding some tooling to publish new versions to NPM is great, but obviously needs to come after #84 or some other similar changes, so this will have to wait a bit. Thank you for working on this, though.

In addition, I’d prefer to have this as a separate workflow that is triggered based on a new tag being added (or manually triggered with the version number to tag with as a workflow-level parameter), and to remove the parts of this workflow that do automatic tagging (the conventional changelog action). I strongly believe that packaged releases should not be automatically published on every change, which this would do, and I also deeply dislike conventional commits-based changelogs (they are better than nothing, but that is about all they are better than — they do a great job of forcing consumers to chase down every PR or commit mentioned, and do a stupendous amount of extra work to understand what’s changed that they need to account for or can make use of; they can make a good starting point to draft release notes from, but that’s not how this workflow works).