Automate the operational part of Wasp releases

[sodic]

This issue only discusses the operational parts of Wasp's release process (e.g., merging branches, drafting a release, tagging the release, etc.). For automating the full release process, see https://github.com/wasp-lang/wasp/issues/2662

As of 0.16.6, Triggering a new release of Wasp involves:

1. Updating and grooming Changelog.md.
2. Double-checking the version in waspc.cabal.
3. Merging those changes (if any) into main
4. Merging release into main
5. Taking a versioned-snapshot of the docs (covered by #292)
6. Fast-forwarding release to main
7. Running the ./new-release script
8. Drafting a release with the release notes
9. Publishing the release when ready (after publishing the docs, mage, etc.)

Even though the steps are pretty short, there's a lot of time between most of them, causing them to fragment the time of whoever is in charge of the release.

Reducing fragmentation by triggering one step after the other somehow (or automating some of them) might be worthwhile