Imagery View does not discard old images when they fall out of bounds

[akhenry]

Summary

In real-time mode the Imagery View should discard images that are older than the configured start bounds as our other telemetry views (such as tables and plots) do.

This is probably a good opportunity to upgrade the imagery view to use TelemetryCollections, as they will handle all of the necessary bounds checks etc. and just emit events when images should be added and removed from the view.

Steps to Reproduce

1. Open example imagery
2. Switch to local clock in the time conductor
3. Set the start bounds to something short (eg. 30 seconds)
4. Wait until the oldest image is older than the configured start bound
5. Observe that it is not removed from the filmstrip view.

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?

[scottbell]

Was able to reproduce; investigating now.

[shefalijoshi]

Verified fixed

[ozyx]

Verified -- Testathon 6/27/22