ci: Automate releasing via bob

[radeksimko]

Context

Releasing currently requires a number of additional steps outside of GitHub. For a simple project with simple release pipeline such as this one, there is no strong benefit to do multi-staged releasing, as some other bigger projects do.

Proposal

Simplify release process by moving promotion steps into a GHA workflow.

TODO

• Create a dedicated GH bot account with appropriate access
• Grant access for proj-terraform-exec-bot to bob repo
• Generate new PAT within the GH bot account ^
• Set PAT as a new secret within this repo BOB_GITHUB_TOKEN
• Update release docs

[kmoe]

Is there a way to have the CLI binaries attached to the GitHub release?

[radeksimko]

Is there a way to have the CLI binaries attached to the GitHub release?

Not directly through CRT (at least not currently), we'd have to build our own workflow to do that.

I'm not sure it's worth uploading it there though, for a couple of reasons:

1. Integrity checking would be quite a manual process (unless someone builds a script around it), which increases the risk folks just wouldn't do it, which then compromises any integrity checking hc-install would do when installing other products. This is also why go install method is discouraged, as that faces the same problem, unless you're careful enough to specify an exact version and hash. Linux package managers and Homebrew do the integrity checking by default.
2. We'd end up spreading our download stats between GitHub and releases.hashicorp.com, where each has different methodology, granularity etc. so getting an accurate stats would be much more difficult.