Increase automation of release job

[ctreatma]

What problem are you facing?

At the moment, the release process for metal-cli is fairly manual:

• Look at the <previous> release version
• Look at the commits to main since the previous release
• Decide on the <next> release version
• Create a tag on main in the format v<next>
• Push the tag to GitHub if it was created locally
• Tag creation triggers a GitHub workflow that runs goreleaser

Now that we are ensuring that the commit log has Conventional Commits tags, we could move all of these steps into the release job so that releasing this CLI is just a matter of pushing a button and letting GitHub Actions handle all of the details.

[ctreatma]

Similar work has been done for other projects where we use Conventional Commits:

• metal-go
• metal-java

In both of those cases, we used https://github.com/cycjimmy/semantic-release-action to drive the release process; that requires adding a .releaserc.json to the project root that configures the necessary release steps.

In this repo, we use goreleaser, which builds the CLI and creates the GitHub release. We may need some investigation to see how to integrate semantic-release-action with goreleaser.

[github-actions]

This issue has been resolved in version 0.23.1 🎉