ci: gate deploy-backend on Supabase secrets presence

[KrishP147]

Fixes #2

main has been red since 6edfb6f because deploy-backend runs with empty SUPABASE_ACCESS_TOKEN / SUPABASE_PROJECT_REF. Adds a check step that writes has_secrets to GITHUB_OUTPUT; CLI setup + deploy steps are skipped (job green, ::notice::) when either secret is unset. deploy-backend now needs frontend-tests.

Note: the job only runs on push to main, so this PR shows it skipped; the main run after merge is the real proof.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[vercel]

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

Project	Deployment	Actions	Updated
nutrisync-frontend	Ready	Preview	Sep 24, 2026 2:05am UTC

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment

Thanks for integrating Codecov - We've got you covered ☂️