Add release automation

### Release / Publishing automation

Add GH Action(s) for release automation.

This is a fairly important piece that I've been missing in my libraries for a bit now and that simplifies the process of publishing into something that requires less effort and can have a quick loop (at least from PR to _patch_ release).
This would also make it less error-prone (even I forget my own release steps occasionally after being away for a while, due to some of the manual portions that I never got around to automating) and easier to hand-off to collaborators to release too; not dependent on a single person to do releases then.

Can see some past thoughts and tools here: https://github.com/jaredpalmer/tsdx/issues/254#issuecomment-604072743

A brief list (will add more over time):
- [`dripip`](https://github.com/prisma-labs/dripip)
- [`auto`](https://github.com/intuit/auto)
- [`craft`](https://github.com/getsentry/craft)

Nice to have: create GH release with the compiled/bundled JS code as well as artifacts (not _just_ the source in the GH release)

### Changelog / Release Notes vs. Publishing

May need/want a separate tool for changelog generation/release notes vs. just publishing a release.

I do more or less like the release notes I've crafted for [TSDX](https://github.com/jaredpalmer/tsdx/releases) and [rpt2](https://github.com/ezolenko/rollup-plugin-typescript2)

Some tools (will add more over time):
- [`changesets`](https://github.com/changesets/changesets)
- [`@agilgur5/changelog-maker`](https://github.com/agilgur5/changelog-maker) (my outdated fork of Node's [`changelog-maker`](https://github.com/nodejs/changelog-maker))

### other potential GH Actions to add

Split off from https://github.com/agilgur5/ts-library-base/issues/1#issuecomment-1154534742

Might also want to add actions for community management, e.g. auto mark as `stale` if no OP response in 30+ days, auto-lock in 90+ days if closed, `stale`, and no response