Automatically publish tagged commits

[MattSturgeon]

We should add a GitHub Actions Workflow that automatically published to GH Releases as well as CurseForge & Modrinth.

The motivation for this is to reduce developer friction when releasing, making it easier to publish smaller releases more often.

Actually creating the release, bumping version numbers, patching the changelog, committing, tagging, & pushing will still be a manual process.

On pushing a non-mc-specific tag

• Create a "GitHub Release"
• Search for matching mc-specific releases
• Link to each
• Add artifacts from each

On pushing a mc-specific tag

• Build artifacts
• Publish to Modrinth
• Publish to CurseForge
• Search for a matching GitHub Release
• Add links & artifacts to the GH Release

Tag format

• Decide on a tag format for mc-specific release commits
  • Previously, -mc1.30 was used
  • It may be easier to use project.version, i.e. +1.20.4 though?

Concurrency

A concurrency group based on the freecam version (mc-generic) should be used to avoid race conditions.

If possible, we should prioritise creating the release before building the artifacts.

Workflows

We'll probably need a few discreet workflows or actions:

• Create GH Release

  • should use changelog provider
  • should include any mc-specific artifacts already built (if possible)

• Build

  • should cache artifacts
  • we may want to run this for all commits, not just tags

• Publish using publishMod

• Publish to existing GH Release

• Update Release (by johnwbyrd, now maintained by ColinPitrat)

  • May prove useful for creating & updating GH Releases from multiple branches