ci(release): Switch from action-prepare-release to Craft

[BYK]

Summary

This PR migrates from the deprecated action-prepare-release to the new Craft GitHub Actions.

Changes

• Migrated .github/workflows/release.yml to Craft reusable workflow
• Updated .craft.yml with versioning.policy: calver

Documentation

See https://getsentry.github.io/craft/github-actions/ for more information.

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (store) Create a trait for the taskbroker store by evanh in #526
• Add python client directory skeleton and move integration tests by markstory in #528
• Add application to schema and API by markstory in #518

Build / dependencies / internal 🔧

• (release) Switch from action-prepare-release to Craft by BYK in #527

• Upgrade to action-setup-venv 3.2.0 by joshuarli in #520

Other

• [STREAM-660] Upgrade Tonic and Sentry Protos by james-mcnulty in #522

---

_{🤖 This preview updates automatically when you update the PR.}

[markstory]

Why? This is going to be noise most of the time. Taskbroker follows calver.

[sentry]

Bug: The scheduled release workflow may fail because it passes an empty string to the version input of the craft action, which might not be handled correctly.
_{Severity: HIGH}

Suggested Fix

To ensure the scheduled job runs correctly, provide a default value for the version input. Setting default: "auto" for the version input would make the behavior explicit for scheduled runs and align with the input's description.

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: .github/workflows/release.yml#L37-L38

Potential issue: The `release.yml` workflow is triggered by both manual
`workflow_dispatch` and an automated `schedule`. When the workflow runs on its schedule,
the `inputs` context is not populated. As a result, the `version` and `force` parameters
passed to the `getsentry/craft` action will be empty strings. It is unknown how the
`craft` action handles an empty string for the `version` input. If it does not default
to an automatic versioning scheme (like calver) when given an empty string, the
scheduled release process will fail.

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

[sentry]

Bug: The workflow runs on a schedule which does not provide inputs. Using ${{ inputs.version }} and ${{ inputs.force }} will result in undefined values during scheduled runs.
_{Severity: HIGH}

Suggested Fix

Provide default values for the inputs to ensure they are defined during scheduled runs. For example, use ${{ inputs.version || 'auto' }}. This explicitly handles the case where the input is not provided, aligning with the likely intended behavior of auto-versioning for scheduled releases.

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: .github/workflows/release.yml#L37-L38

Potential issue: The `release.yml` workflow is triggered by both `workflow_dispatch` and
`schedule`. The `workflow_dispatch` event provides `inputs.version` and `inputs.force`,
but the `schedule` event does not. When the workflow runs on its schedule, the values
passed to the `craft` action for `version` and `force` will be empty or undefined. While
the `craft` action might be configured to handle this by auto-generating a version, this
behavior is unconfirmed. If the action does not gracefully handle empty inputs, the
scheduled release process could fail.

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