Wire Bugsnag into the orchestrator

[morgan-wowk]

TL;DR

Integrates Bugsnag error reporting into the orchestrator to capture system-level exceptions.

What changed?

Bugsnag instrumentation is now initialized at orchestrator startup with the service name tangle-orchestrator. System errors recorded via record_system_error_exception now notify Bugsnag with the associated execution ID. Additionally, any unhandled exception that escapes the main run_loop is reported to Bugsnag before being re-raised.

How to test?

Trigger a system error during an execution and verify that the exception appears in Bugsnag with the correct execution ID attached. Also verify that an unhandled exception in run_loop is reported to Bugsnag under the tangle-orchestrator service.

Why make this change?

Previously, system errors were only tracked via metrics and local logs, making it difficult to investigate failures in production. Routing these exceptions to Bugsnag provides better visibility and alerting for unexpected orchestrator errors.

[morgan-wowk]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Add Bugsnag error grouping with stable normalized keys #234
• Wire Bugsnag into the orchestrator #232 👈 (View in Graphite)
• Wire Bugsnag into the API server #231
• Add Bugsnag instrumentation module #230
• Add bugsnag Python SDK dependency #229
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.