Independent time conductor related handling for plot synchronization.

[shefalijoshi]

Closes #7737

Describe your changes:

Ensure that the mode set when independent time conductor is enabled/disabled is propagated correctly.

Also ensure that global time conductor changes are not picked up by the independent time conductor when the user has enabled it at least once before

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?

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 65.32%. Comparing base (5be103e) to head (5094c19).

Files with missing lines	Patch %	Lines
src/api/time/IndependentTimeContext.js	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7956      +/-   ##
==========================================
+ Coverage   57.57%   65.32%   +7.74%     
==========================================
  Files         678      436     -242     
  Lines       27428    13648   -13780     
  Branches     2691        0    -2691     
==========================================
- Hits        15793     8915    -6878     
+ Misses      11294     4733    -6561     
+ Partials      341        0     -341     

Flag	Coverage Δ
e2e-ci	62.77% <83.33%> (-0.05%)	⬇️
e2e-full	41.97% <16.66%> (+<0.01%)	⬆️
unit	?

Files with missing lines	Coverage Δ
src/api/time/TimeAPI.js	91.17% <100.00%> (+0.26%)	⬆️
src/api/time/IndependentTimeContext.js	68.75% <80.00%> (-13.19%)	⬇️

... and 365 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

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

[unlikelyzero]

@shefalijoshi i think the best test is the first example of steps to reproduce:

No fixed time change warning prompt

Create an overlay plot, add telemetry to it, and save
View the plot in realtime mode
hover over the plot and click Pause
hover over the plot and click Synchronize with Time Conductor
Observe you get a warning message and are switched to Fixed time mode (This is expected behavior)
Toggle the independent time conductor, then toggle the indepedent time conductor off
Change the time conductor back to realtime mode.
Repeat steps 4 and 5 to pause and sync time with conductor
Observe this time there is no warning message.

[davetsay]

Looks good. I have a couple requests. One is inline, and the other is can you add test coverage?

I'll close the other related PR as this is the correct fix.

[davetsay]

I think we can use structuredClone over JSON cloning, unless there is a good reason not to.