What changed

Drops the explicit gh workflow run release-tag.yml step from release-prepare.yml. Since the prepare job now pushes with a GitHub App token (not GITHUB_TOKEN), the natural on: push: tags: ['v*'] trigger fires release-tag.yml automatically — the explicit dispatch was originally a workaround for GITHUB_TOKEN's trigger suppression and is now redundant.

Without this, every release dispatched two duplicate release-tag.yml runs (one from the natural push trigger, one from the explicit dispatch), queued back-to-back via the concurrency group. The first release run (#25205749266) triggered exactly this.

Technical Context

• App-token pushes do fire on: push workflow triggers — only GITHUB_TOKEN-driven pushes are suppressed by GitHub
• Removed Job 1's Verify gh auth and dispatch capability step — its sole purpose was sanity-checking that the now-removed dispatch step would work
• Tightened Job 1 permissions from contents: read, actions: read to just contents: read; dropped Job 1's job-level GH_TOKEN env (no gh calls remain in Job 1)
• Job 2's existing concurrency on release-tag.yml (group: release-${{ github.ref_name }}) still protects against accidental duplicates if anyone manually dispatches the workflow at the same ref