ci chore: move to version tag triggered release scheme

[Lee Read]

Noticed that I still have a GitHub Actions GUI triggered release strategy here.

This is a reminder to switch to a git version tag triggered release scheme, which is the preference of those with an interest on the clj-commons team.

This work was recently done on pomegranate and even more recently rewrite-clj.
So I'll steal from those projects.

[Lee Read]

Note to self: look at refining how the publish flow is triggered.

We want it triggered by a new version tag, but ideally, we don't want this triggering to happen from forks. It's not the end of the world to do this, the attempt to publish will fail, but it is confusing and annoying for contributors when all they've done is innocently synched with upstream.

I've done a bit of digging, and I don't see anything at the workflow level, but at the job level, we might be able to add a check like:

if: github.repository_owner == 'clj-commons'

To skip all jobs in the publish flow unless it is run from clj-commons.