Add release-publishing workflow using GoReleaser

[aidansteele]

Here's a PR that will use GoReleaser for publishing new releases. A few things to note:

1. You should create a GitHub personal access token to allow GoReleaser to update your Homebrew tap repo. The token generated by GitHub Actions won't suffice for cross-repo access. I recommend creating a fine-grained access token that has Read and write access to Contents for just that specific repo. You should then save it as GORELEASER_HOMEBREW_TAP_TOKEN in the Actions secrets for this repo.
2. The workflow to create releases is to create a Git tag. That will trigger the workflow to run GoReleaser, which will populate the "release" info in GitHub.
3. I changed the Version var to version. This variable will be populated at compile-time by GoReleaser with the name of the tag. Cmd+F ldflags on this page for more info.

[aidansteele]

Personally, the way I create new tags is:

• Click Draft a new release on the releases page.

• Click Choose a tag, type in the new tag name and click create new tag on publish

• Leave everything else untouched and click Publish release. This will trigger the GoReleaser workflow. GoReleaser will populate the release notes and attach the new binaries to this release.

[benkehoe]

Why not export the version, if this is used as a module in a bigger program?

[jamietanna]

Doing this also loses go install'd versioning. I've recently been using https://github.com/carlmjohnson/versioninfo/ which works for both goreleaser and go install, and should also work when imported as a library

[benkehoe]

have you ever tried to make an RPM easily available for installation on Amazon Linux? I'm not clear if that would have to involve getting it in a particular yum repo or what