[TelemetryAPI] Subscriptions need to be unique based on request options

[jvigliotta]

VIPEROMCT-552, VIPEROMCT-553

Summary

The Telemetry API's subscribe method will currently differentiate subscriptions based on a combination of domain object key string and request strategy (latest, batch, etc). This works for most situations, but it fails in situations where filter options are passed in with the request.

Expected vs Current Behavior

Subscriptions should be unique based on domain object key string and request options (which will include strategy as well as filter options, among other options). Currently it's only domain object key string and request strategy.

Steps to Reproduce

1. Create a display layout with two tables that have the same domain object
2. Set different filters on each table
3. Notice ONE of the tables will not be filtering correctly (historical will filter correctly)
4. Be amazed

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