fix(release): rebase tap clone before push to avoid non-fast-forward

[sahil87]

What

Insert git pull --rebase --autostash before the git push in the Update Homebrew tap step of release.yml.

Why

Release run for v0.0.12 failed at the tap-update step:

! [remote rejected] main -> main (cannot lock ref 'refs/heads/main':
   is at 75d6efed... but expected d26fb924...)
error: failed to push some refs

The step did clone → edit formula → commit → push with no reconciliation. When homebrew-tap's main advanced between the clone and the push (concurrent writers to the shared tap repo), git rejected the push as a non-fast-forward — failing the release after the GitHub Release and binaries had already been published.

Fix

Rebase the formula commit onto the current remote tip before pushing. --autostash is defensive (there's nothing dirty in the fresh clone, but it costs nothing).

Notes

• The failed v0.0.12 run was already re-run and is green; the tap formula is at version "0.0.12". This PR just prevents recurrence.
• This handles a single collision. If the tap ever sees sustained concurrent writers, a fetch-rebase-retry loop would be the next step — not needed for a single-project tap.
• Out of scope: a Node 20 → 24 action-deprecation warning surfaced on the same run (actions/checkout, actions/setup-go, action-gh-release). Unrelated to this failure; can be addressed separately.

🤖 Generated with Claude Code