fix(automations): pin supabase CLI to v2.98.2

[sw-factory-automations]

What

Supabase CLI v2.99.0 (released today) changed release asset naming to include the version number in the filename (supabase_2.99.0_linux_amd64.tar.gz instead of supabase_linux_amd64.tar.gz). This breaks supabase/setup-cli@v1's download URL construction when using version: latest, causing a 404 on all PR staging checks.

All open PRs (#1139, #1140) are blocked by this failure.

Fix

Pin both the staging and deploy jobs to version: 2.98.2 until setup-cli is updated to handle the new naming convention.

Verification

• https://github.com/supabase/cli/releases/download/v2.98.2/supabase_linux_amd64.tar.gz → 302 ✅
• https://github.com/supabase/cli/releases/download/v2.99.0/supabase_linux_amd64.tar.gz → 404 ❌

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
memo	Ready	Preview, Comment	May 18, 2026 11:06am

[sw-factory-automations]

✅ UI verification skipped — no UI files changed (only .github/workflows/deploy-migrations.yml).

[sw-factory-automations]

✅ Post-merge verification passed.

PR scope: CI workflow change only (.github/workflows/deploy-migrations.yml) — no app code modified, no Vercel deployment triggered.

Ad-hoc smoke tests (all passed):

• ✅ Landing page (/) — loads, has title
• ✅ Sign-in page (/sign-in) — renders email input
• ✅ Health endpoint (/api/health) — returns OK
• ✅ Authenticated login flow — redirects to workspace
• ⏭️ Skipped: /dashboard (not yet built), editor route (no page buttons in test workspace)

E2E suite: 394/405 tests passed. 11 failures are pre-existing and unrelated to this PR (which only changed a GitHub Actions workflow file):

• account-deletion (3): alertdialog not opening after button click
• database-bulk-select (2): action bar visibility timing issues
• database-column-reorder (3): test expectations don't match current column header list
• database-csv-export (2): cell count mismatch and browser context teardown
• database-duplicate-row (1): browser context closed during setup

These failures cannot be caused by a Supabase CLI version pin in CI. No regression detected.