event listeners to Time API don't fire if a previous event listener errors

[davetsay]

Summary

The error in gauges in #7908 causes time conductor to not display bounds on update.

Expected vs Current Behavior

The time conductor bounds should have updated regardless of other listeners on boundsUpdated

Steps to Reproduce

1. Create a gauge object
2. Add telemetry to the gauge object
3. Make the telemetry a missing object
4. delete or modify the identifier of the object from the persistence store directly
5. Navigate to the gauge object
6. change the bounds on the time conductor
7. Observe that the time conductor does not update to show the new bounds, even though all telemetry in view respects the new bounds

Environment

• Open MCT Version:
• Deployment Type:
• OS:
• Browser:

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information