ref: use generic Docker image release pipeline

[aldy505]

To help with getting this to self-hosted. If this PR is merged, we won't automatically generate the release for self-hosted, the issue on the publish repo can be safely rejected.

[sentry]

Bug: The .craft.yml configures craft to wait for a 'Publish' GitHub status check that no workflow sets, blocking releases.
_{Severity: CRITICAL | Confidence: 1.00}

🔍 Detailed Analysis

The .craft.yml file configures statusProvider to wait for a GitHub status check named 'Publish'. However, no existing workflow in the repository sets this 'Publish' status. This will cause the craft CLI tool, invoked by action-prepare-release in release.yml, to indefinitely wait for a non-existent status, blocking the release pipeline from completing successfully.

💡 Suggested Fix

Either remove the statusProvider configuration from .craft.yml, ensure a workflow sets the 'Publish' status, or change the context name to an existing status.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .craft.yml#L8-L9

Potential issue: The `.craft.yml` file configures `statusProvider` to wait for a GitHub
status check named 'Publish'. However, no existing workflow in the repository sets this
'Publish' status. This will cause the `craft` CLI tool, invoked by
`action-prepare-release` in `release.yml`, to indefinitely wait for a non-existent
status, blocking the release pipeline from completing successfully.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

_{Reference_id: 2703558}

[Swatinem]

rubberstamping, I don’t really understand all the details here.

[Swatinem]

as you have pinned all the other actions to the SHA in a different PR, might as well do that here as well :-)

Dismissing review without context

[jan-auer]

Let's please wait with this until we have reached a stable integration of Objectstore into Sentry. After this, we can include it in self-hosted.