Re-jiggering/cleaning up Auto Release process

[seanspeaks]

Request for Assistance- Current state

Right now we have an okay approach to releases. Any PR to main in /frigg and /api-module-library, as long as they're tagged correctly, are successfully releasing with auto.

Updates requested

Rock solid "next" pre-releases

But, I'd like to have pushes to the next branch automatically release a next tagged version. Actual version number can/should be determined by the PR label (major|minor|patch or via Auto's automatic detection.

Tag and changelog and versioning cleanup

Additionally, I'd like to clean up our tags and changelog and versioning so that we've got a sane history when you look at the git tags etc.

Changelog updates- thoughtful updates and sane overrides/editing abilities; default templates for contributors

And (I think lastly) I'd like to be more thoughtful about changelog updates... automatic ones and having a template for PRs/commits so that devs collaborating and opening PRs have a straightforward way of adding notes (and that maintainers have an easy way to change/edit/override the changelog notes as well).

Versioning standardized for /frigg and /api-module-library

Okay, truly lastly, I want to decide on and stick to a versioning approach for all of the packages. Maybe unified versioning even if no changes actually were made? That would work with /frigg core packages, as those aren't going to be rapidly updated. That will not be tenable with api-module-library, however. We'd want to anchor those to the major frigg core version, but any change (minor / patch) to a given API module package should not auto-bump all of the other packages. Over time that repo is likely to grow to thousands of modules, and have hundreds of updates on a daily or weekly basis, which would lead to chaos in releases (not to mention a laborious pipeline).