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

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).

---

Bug Fixes 🐛

• (ios) Fix UserFeedback not being sent on iOS by romtsn in #503

Build / dependencies / internal 🔧

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

---

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

[sentry]

Bug: The optional force input lacks a default. If not provided, GitHub Actions passes an empty string, which could be misinterpreted by the downstream craft action, potentially forcing a release.
_{Severity: CRITICAL}

Suggested Fix

To ensure predictable behavior, explicitly handle the empty string case. Add a default value for the force input, such as default: 'false', or use a conditional step to set a default if the input is an empty string, like force: ${{ github.event.inputs.force || 'false' }}.

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#L15-L17

Potential issue: The `release.yml` workflow defines the `force` input as optional
(`required: false`) without a default value. When a user triggers this workflow without
specifying the `force` input, GitHub Actions will pass an empty string `""` to the
`getsentry/craft@v2` action. The behavior of the `craft` action when receiving an empty
string for a boolean input is unknown. If it interprets an empty string as `true`, it
could lead to unintentionally forced releases even when release-blockers are present. If
it fails validation, the workflow will break.

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