ci: publish vroom to GHCR and provide a tagged release on GHCR

[aldy505]

Similar work with these PRs:

• feat(release): Tag images with release version. relay#4532
• feat(release): Tag images with release version. symbolicator#1635
• feat(ci): tag GHCR image with release version snuba#6997
• feat(ci): tag GHCR image with release version sentry#88181

While also trying to provide a solution (or at least an alternative) for this issue: getsentry/self-hosted#3593

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[BYK]

Let's definitely not do this and move the actual build to GitHub Actions. Otherwise you are just wasting CPU cycles and holding up workers until the Google build is done.

Alternatively, you can just another target in .craft.yml which does exactly what you do here.

[BYK]

I guess? :D

[BYK]

@asottile-sentry for the review, especially on required checks.

Ah, the failure was due to permissions. Retried from my account, let's see if it goes through.

[aldy505]

@asottile-sentry for the review, especially on required checks.

Ah, the failure was due to permissions. Retried from my account, let's see if it goes through.

@BYK I believe it was due to this https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#pushing-container-images

When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see Configuring a package's access control and visibility. You can link a published package to a repository using the user interface or command line. For more information, see Connecting a repository to a package.