🛡️ Sentinel: [HIGH] Fix PII leak in Sentry integration

[google-labs-jules]

🚨 Severity: HIGH\n💡 Vulnerability: User email was set in the global Sentry scope and manually cleared after an asynchronous API call. If the call failed, the PII would leak into subsequent unrelated error reports.\n🎯 Impact: PII leakage in external error reporting system.\n🔧 Fix: Used a defer block to guarantee cleanup of the Sentry scope regardless of how the execution block exits.\n✅ Verification: Code review confirms defer block is used for cleanup.

---

PR created automatically by Jules for task 6763581757235380242 started by @TytaniumDev

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.