fix: Add namespace correlation to sentry monitoring

[VVoruganti]

Summary by CodeRabbit

• Chores
  • Improved error reporting metadata so issues can be more easily associated with the correct deployment namespace.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3be9d4cb-7d02-46cf-83e3-078f9f756eb3

📥 Commits

Reviewing files that changed from the base of the PR and between 63ea82c and e88e026.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• src/telemetry/sentry.py

---

Walkthrough

Sentry initialization now sets a global scope tag named "namespace" using the configured settings.NAMESPACE value, causing subsequent Sentry events to include this tag.

Changes

Sentry namespace tag

Layer / File(s)	Summary
Set global namespace tag src/telemetry/sentry.py	initialize_sentry() applies a global scope tag "namespace" set to settings.NAMESPACE after SDK initialization.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A tiny tag, hopped in with glee,
"namespace" now for all to see,
Sentry events, marked with care,
Know just which warren sent them there. 🐇
A small hop, but a tidy trace!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the change: Sentry now adds the configured namespace for monitoring correlation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch vineeth/dev-1977

---

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