Create a "release" workflow

[OpenBagTwo]

This will involve a bit of research.

Creating a release should:

• build the mod for all supported Minecraft versions
• build the resource pack generator for all supported platforms
• add the binaries and jars to the release
• publish the mod jars to Modrinth
• publish the mod jars to Curseforge

I'm expecting to do the last three manually for the initial release.

[OpenBagTwo]

I've created a "lightweight" tag to specify the first release candidate (:crossed_fingers: the code is ready to ship for the initial release) and successfully gotten jgitver to pick it up. Some findings:

• If a tag isn't "annotated" it will always show the distance after, even if the distance is zero
• While I got it to show commit hashes and "dirty" tags, I can't get the character before the distance to be "+" instead of "-", but it looks like "+" tags are canonically ignored for precedence anyway, so oh well.
• The version must be of the form MAJOR.MINOR.PATCH--no leaving off the patch (so the first release will be v0.1.0 and not v0.1 as I was intending)
• The "v" appears to be optional, at least 🙃
• v0.1.0-rc1 was kosher--v0.1.0-rc.1 was not

[OpenBagTwo]

+1 especially if I plan to keep support going all the way back to 1.19[.0]. The v0.1.2 release has a total of six builds, which was a pain in the toucans to upload to Modrinth, and doubly so with Curseforge.