[Remote Clock] Wait for first tick and recalculate historical request bounds

[ozyx]

Closes #5221

Describe your changes:

Adds a TelemetryRequestInterceptor. Block historical requests until the remote clock receives its first tick, and then use the interceptor to recalculate the request bounds.

Tests for TelemetryRequestInterceptor to be added in a future PR.

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 change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

Author Checklist

• Changes address original issue?
• Unit tests included and/or updated with changes?
• Command line build passes?
• Has this been smoke tested?
• Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

• Changes appear to address issue?
• Changes appear not to be breaking changes?
• Appropriate unit tests included?
• Code style and in-line documentation are appropriate?
• Commit messages meet standards?
• Has associated issue been labelled unverified? (only applicable if this PR closes the issue)
• Has associated issue been labelled bug? (only applicable if this PR is for a bug fix)

[ozyx]

@unlikelyzero @akhenry :

A bunch of these imagery view tests are failing now because the added interceptor logic is adding more time, and Vue doesn't have the opportunity to update in time. If we add more await Vue.nextTick(), we can get these to pass (bleh).

Most of these actions are already covered by e2e tests, should we instead convert the failing tests to e2e tests and thus maintain the same coverage?

[akhenry]

Looking really good! thanks also for converting the TelemetryAPI to an ES6 module, and for the excellent jsdocs.

There are some minor changes that I think will improve this (and avoid potential unexpected regressions).

[codecov]

Codecov Report

Merging #5433 (a09db30) into release/2.0.5 (a09db30) will not change coverage.
The diff coverage is n/a.

❗ Current head a09db30 differs from pull request most recent head 45afaed. Consider uploading reports for the commit 45afaed to get more accurate results

@@              Coverage Diff               @@
##           release/2.0.5    #5433   +/-   ##
==============================================
  Coverage          52.68%   52.68%           
==============================================
  Files                590      590           
  Lines              21761    21761           
  Branches            2041     2041           
==============================================
  Hits               11465    11465           
  Misses             10036    10036           
  Partials             260      260           

Flag	Coverage Δ
e2e-ci	37.39% <0.00%> (ø)
unit	50.94% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a09db30...45afaed. Read the comment docs.

[unlikelyzero]

e2e improvements look great!

If you have time before Andrew's review, you might want to put in a Remote Clock stub that captures this behavior as filed in the initial bug.

/e2e/tests/plugins/remoteClock

//boilerplate
test.describe('Remote Clock Tests', () => {
    test.fixme('Remote Clock accepts telemetry on initial load', async ({ page }) => {
    //addInitScript to with remote clock
    //Navigate directly to telemetry by URL OR by clicking time conductor
    };
}