Improved buffering

[akhenry]

NOTE: nasa/openmct#7837 will need be merged before this.

1. Merge Improve telemetry buffering implementation nasa/openmct#7837
2. Update package.json to point it to npm latest

Adapts the openmct-yamcs plugin for the API changes in nasa/openmct#7838

Describe your changes:

• Modifies telemetry subscription handling in openmct-yamcs adapter to support improvements to the telemetry API in Open MCT.
• Removes the Yamcs-specific batching strategy previously required . Open MCT now uses a more flexible one-size fits all strategy
• Adds a new test to catch the failure mode identified in the previous strategy.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Is this a notable change that will require a special callout in the release notes? For example, will this break compatibility with existing APIs or projects that consume these plugins?

Author Checklist

• Changes address original issue?
• Tests included and/or updated with changes?
• Has this been smoke tested?
• Have you associated this PR with a type: label? Note: this is not necessarily the same as the original issue.
• Have you associated a milestone with this PR? Note: leave blank if unsure.
• Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

• Changes appear to address issue?
• Reviewer has tested changes by following the provided instructions?
• Changes appear not to be breaking changes?
• Appropriate automated tests included?
• Code style and in-line documentation are appropriate?

[unlikelyzero]

test('Does not drop telemetry when a burst of telemetry greater than the sharedbuffer arrives')

[akhenry]

Good call, will do.

[shefalijoshi]

This looks fine overall, however, the staleness and remote clock changes should be moved out into separate PRs.

[shefalijoshi]

I wasn't able to test staleness successfully, but we can do this once it's deployed to banner or shehulk. Looks good to me.

[akhenry]

Test was failing due to genuine bug introduced in this refactor of telemetry batching. Previously housekeeping WebSocket messages bypassed the throttling / batching process altogether, which meant that important housekeeping messages (such as those that go back and forth when setting up a telemetry subscription) were never dropped.

With this refactor the WebSocket buffering code was greatly simplified, removing the special handling for housekeeping messages. One of the automated tests triggered an edge case where throttling is induced during the initial handshaking that takes place when initializing a subscription, causing some subscriptions to never get established properly. Luckily our tests caught this.

I made a small change to the telemetry throttling implementation so that instead of throttling all messages when the UI thread is overloaded, a regex can optionally be supplied that is used to decided whether a given message should be throttled. This allows us to avoid culling housekeeping messages.

[shefalijoshi]

Looks good