Introduce release automation

[timflannagan]

Goal: introduce automation that's responsible for creating a github release when a new tag has been pushed to this repository's git remote.

AC:

Note: This is more-or-less mirrored from rukpak/combo's release pipeline setup

• Introduce a .goreleaser.template.yaml file
• That template file contains references for building/pushing container images, and creating github releases
• Add a Makefile target that installs goreleaser as a tool dependency
• Add a Makefile target that generates a goreleaser.yaml file using envtest on that .goreleaser.template.yaml file
• Add a Makefile target that generates a goreleaser.yaml file, and runs goreleaser with the provided arguments configuration
• Add a GHA workflow that runs goreleaser on every PR, push to the main branch, and new tag event triggers

[github-actions[bot]]

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

[tylerslaton]

This issue looks good and RukPak should be a good guide here for how to accomplish this. However, the one thing to keep in mind is what exactly we want the release artifact to be - a binary, yaml stream, etc.

[github-actions[bot]]

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

[timflannagan]

@perdasilva @joelanford Just going through my open issues to see what can be closed: is this still an issue, or can it be closed?

[github-actions[bot]]

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.