fix(app): sync robot time with app time on connect

[mcous]

Overview

This PR wires the app up to the time endpoints added in #6403. When the app requests to connect over RPC, it will also hit GET /system/time and, if the time is mismatched by more than 60 seconds, the app will send a PUT /system/time request to get things sync'd.

Closes #3872

Changelog

• feat(app): sync robot time with app time on connect

Review requests

Smoke test:

0. Ensure your robot is running software that includes the time endpoints added in feat(robot_server): add system/time GET & PUT endpoints #6403
1. SSH into your robot and mess up the time
   1. systemctl disable systemd-timesyncd
   2. date -s 10:10
2. Open the Opentrons App
3. Click the connect toggle or button
   • GET /system/time request goes out
   • PUT /system/time request goes out
   • date in the robot's terminal reports the same time (in UTC) as your computer
4. Disconnect and connect again
   • GET /system/time request went out
   • PUT /system/time request does not go out because time is already synced

Risk assessment

Medium low. Thoughts + notes:

• Time is a funny thing to mess with
• If timesyncd is running and the robot has NTP access, the NTP time will be reasserted quite quickly
  • The app only attempts to sync at connect, so we won't get into an edit war with the system time
• If the robot is on an older software version, GET /system/time will 404
  • The app will only try to send the PUT if the GET succeeds
  • We could (should?) add systemTime to the health links so we can check capabilities ahead of time
  • Until then, the 404 will show up in the logs like it does when the app tries to fetch calibration data from out of date robots

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (edge@b5a59e0). Click here to learn what that means.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             edge    #6501   +/-   ##
=======================================
  Coverage        ?   56.56%           
=======================================
  Files           ?     1073           
  Lines           ?    16549           
  Branches        ?        0           
=======================================
  Hits            ?     9361           
  Misses          ?     7188           
  Partials        ?        0           

Impacted Files	Coverage Δ
app/src/robot-admin/epic/index.js	100.00% <ø> (ø)
app/src/robot-admin/constants.js	100.00% <100.00%> (ø)
app/src/robot-admin/epic/syncTimeOnConnectEpic.js	100.00% <100.00%> (ø)
app/src/robot-api/constants.js	100.00% <100.00%> (ø)
...reators/atomic/thermocyclerAwaitProfileComplete.js	100.00% <0.00%> (ø)
app/src/pages/Robots/InstrumentSettings.js	0.00% <0.00%> (ø)
...otocol-designer/src/components/ComputingSpinner.js	0.00% <0.00%> (ø)
...ry/src/components/website-navigation/MenuButton.js	0.00% <0.00%> (ø)
...p/src/components/CalibratePanel/CalibrationData.js	100.00% <0.00%> (ø)
...src/components/LabwareDetails/LabwareDetailsBox.js	0.00% <0.00%> (ø)
... and 1067 more

---

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 b5a59e0...cd2e841. Read the comment docs.

[sanni-t]

If the robot is on an older software version, GET /system/time will 404
The app will only try to send the PUT if the GET succeeds
We could (should?) add systemTime to the health links so we can check capabilities ahead of time
Until then, the 404 will show up in the logs like it does when the app tries to fetch calibration data from out of date robots

I'll make a (follow-up) PR to add systemTime to health links now.

[sanni-t]

LGTM!
A robot connection correctly updates time or does nothing, based on robot's time status.
Approved pending that test mentioned by @amitlissack