Epic: release automation

[gaktive]

Problem Description

Though the release process is mostly manageable by those who pull the levers, when it comes to building, signing, tagging and announcing, we should look at automating what we can so that others can do the release.

This may be complicated based on the platforms we have to target and having systems to do that but this ticket should have subtasks tied to what we can do to make this process available via push button.

Possible tasks

• Epic: Generate screenshots as part of the CI for docs, #2 #3434
• Final smoke test: download binaries from draft release, make sure they are signed, do install, and start up a cluster. Could publish the release if everything passes. — CI: Add workflow to do a simple smoke test from a release #6691

[mook-as]

We've done the release automation we intend to do for now; there isn't any manual steps that doesn't involve checking the output before proceeding. Closing.