Set up release process

[Firehed]

Ideally, I would like this to be done purely in GHA. There's very likely some off-the-shelf system to manage this.

Rough vision: Actions > Create Release Type: Major, Minor, Patch(default) Source branch: main

When run, it would:

• check out the code
• bump the version in package.json (and lock?) based on the release type
• create a git tag matching the new version
• push both, create a (draft?) release in github using this tag
• publish to npm

There's probably some stuff that doesn't flow quite right in there, but that's the general concept.

Realistically a major version is important enough that automating it may be a bad idea. TBD.

[Firehed]

Looks like most of this can be done via the npm version [...] command. It will both bump the version and tag the commit. From there, it needs to be published, and possibly have some vX.Y.Z-next set up for future commits.

[Firehed]

There is also the current minor snag of updating the version referenced in the README, but that can probably get reworded to make it a nonissue.