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 🐛

• Accept chunked ProGuard uploads by jpnurmi in #140

Build / dependencies / internal 🔧

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

---

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

[vaind]

Does this mean we need to type literal "auto" in the input? What version do we get then?

[vaind]

To answer my own question...

it's automatically inferred form commits if not provided

[github-actions]

	Warnings
⚠️	Could not load custom Dangerfile: .github/test-dangerfile-curl.js Error: ENOENT: no such file or directory, lstat '/github/workspace/.github/test-dangerfile-curl.js'

Generated by 🚫 dangerJS against 10cbfa5

[vaind]

According to the Craft documentation, there's a simpler reusable workflow approach available:

 jobs: release: uses: getsentry/craft/.github/workflows/release.yml@v2 with: version: ${{ inputs.version }} secrets: inherit 

Is there a reason not to use the reusable workflow pattern for releases as well?

[vaind]

replaced by #148 to address the comments & remove the unrelated switch to show changelog preview