chore: Set Bugsnag release stage based on TANGLE_ENV variable

[morgan-wowk]

Description

Enhanced Bugsnag error reporting configuration to require both API key and environment variables for initialization. Added VITE_TANGLE_ENV environment variable to set the Bugsnag releaseStage and prevent unnecessary API calls for container execution states when containers are in expected non-execution states.

Related Issue and Pull requests

Type of Change

• Bug fix
• Improvement
• Documentation update

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Screenshots (if applicable)

Test Instructions

1. Set up environment variables in .env file:

   VITE_BUGSNAG_API_KEY=your-api-key
   VITE_TANGLE_ENV=production

2. Verify Bugsnag initializes only when both variables are present
3. Test that error reporting is disabled when either variable is missing
4. Verify that container execution state API calls are skipped for containers in states like INVALID, UNINITIALIZED, QUEUED, WAITING_FOR_UPSTREAM, SYSTEM_ERROR, CANCELLED, and SKIPPED
5. Use the "Throw error" button on the home page to test error reporting functionality

Additional Comments

The changes prevent unnecessary API calls for container execution states when containers are in expected states where execution records may not exist yet. This optimization reduces backend load and eliminates expected 404 errors from the logs.

[github-actions]

🎩 To tophat this PR:

You can add the following URL parameter to your browser to tophat this PR:

`?tophat_location=bugsnag-release-stage/53baa16`

---

[morgan-wowk]

• chore: Set Bugsnag release stage based on TANGLE_ENV variable #1872 👈 (View in Graphite)
• master

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