fix: [ci-fix] pin supabase CLI to v2.99.0 instead of latest

The supabase/setup-cli@v2 action with version: latest returns HTTP 404
when resolving the download URL. Pinning to the current release (2.99.0)
avoids the transient resolution failure.

Co-authored-by: Ona <no-reply@ona.com>

Author: sw-factory-automations

.github/workflows/deploy-migrations.yml

@@ -45,7 +45,7 @@ jobs:
       - uses: supabase/setup-cli@v2
         if: steps.check-secrets.outputs.skip == 'false'
         with:
-          version: latest
+          version: 2.99.0
 
       - name: Link staging project
         if: steps.check-secrets.outputs.skip == 'false'
@@ -76,7 +76,7 @@ jobs:
 
       - uses: supabase/setup-cli@v2
         with:
-          version: latest
+          version: 2.99.0
 
       - name: Link Supabase project
         run: supabase link --project-ref $SUPABASE_PROJECT_ID