Provide a lightweight sparkline visualization for numeric telemetry

Is your Featured request related to a problem? Open MCT provides several plotting views for telemetry, but there is a use case for a much more compact visualization of a single numeric telemetry stream.

In operational displays, it can be useful to show the recent behavior and trend of a telemetry value without dedicating the space or visual complexity of a full plot. A small sparkline can provide this context while allowing the operator to keep more telemetry and other mission information visible at the same time.

The desired visualization is particularly useful when a telemetry value needs to be monitored continuously for changes or trends, rather than analyzed in detail. The visualization should still behave as a native Open MCT view: it should respect the current time context, display historical telemetry when opened, and update as new telemetry arrives.

Describe the Solutions you would like Provide a lightweight sparkline view for numeric telemetry that:

• Displays the telemetry history for the current Open MCT time window.

• Updates as new realtime telemetry becomes available.

• Remains synchronized with the Open MCT Time Conductor.

• Uses telemetry metadata to identify and format the numeric value being plotted.

• Provides a compact visualization suitable for dashboards and other space-constrained layouts.

• Avoids continuously rendering when neither the telemetry nor the time window has changed.

The implementation could be provided as an Open MCT visualization/plugin and should use the existing telemetry and time APIs rather than maintaining an independent telemetry or time-management mechanism.

Describe alternatives you have considered The existing plot views provide a more detailed visualization, but they are not always appropriate when the primary requirement is to communicate the recent trend of a single telemetry value in a small amount of screen space.

A custom external visualization could also provide a sparkline, but that would require applications integrating Open MCT to maintain their own visualization and would make it harder to keep the visualization synchronized with Open MCT's telemetry and time APIs.

Additional context PR #8390 explores this use case with an Astonishing Sparkline view.

The current implementation is intended as a lightweight canvas-based visualization and uses Open MCT's telemetry collection and Time API so that historical data, realtime telemetry, and changes to the active time context can be represented by the view.

The intent of this issue is to establish the use case and desired Open MCT capability independently of the particular implementation in PR #8390.