Chore: Enable email verificaiton on Stage

[Meldiron]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• New Features
  • Cloud Stage now enforces email verification. Users signing in will be prompted to verify their email before accessing the console, enhancing account security.
  • Existing sessions may continue until they expire; new logins will require verification.
  • This change applies only to the Cloud Stage environment and does not impact other environments.

[coderabbitai]

Walkthrough

The CI workflow for publishing was modified to change the Docker build argument PUBLIC_CONSOLE_EMAIL_VERIFICATION from false to true in the publish-cloud-stage. No other build arguments, steps, control flow, or error handling in the workflow were altered. There are no changes to exported or public entity declarations.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly encapsulates the main change by enabling email verification in the Stage environment, which directly corresponds to the updated Docker build argument in the publish workflow. It is concise and clearly highlights the core purpose of the pull request.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore-enable-stage-emai-verification

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0931a2 and d982b81.

📒 Files selected for processing (1)

• .github/workflows/publish.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build
• GitHub Check: e2e

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}