fix(app, react-api-client): rely on subsystem status before instrument status

[smb2268]

fix RQA-1585

Overview

We can't rely on the /instruments endpoint response while a subsystem update is ongoing. Instead, we first need to poll for the presence of an update on a given subsystem.

Test Plan

1. Attach an instrument that needs an update during a firmware update flow. Observe that when after the firmware update takes place, you don't see an "instrument not attached" screen before you see a success screen.
2. Update the firmware of an instrument via the ODD. On desktop, watch the instrument card for the corresponding instrument. The instrument card should display a subsystem update in progress until the update is complete, and then show the instrument card for an attached instrument.

Changelog

1. In the firmware update modal, once the update is done refetch the instruments. If the instrument is ok, proceed to the results screen. If it is still not ok, wait another 10 seconds before proceeding.
2. In the gripper and pipette cards, continuously poll for a subsystem update. If an update is ongoing, rely on that information to show the "bad" instrument card and update banner. If it is not, rely on the /instruments endpoint response for what to show.

Review requests

Run through the test plan

Risk assessment

Low

[codecov]

Codecov Report

Merging #13588 (b53306d) into chore_release-7.0.0 (4ec3bb7) will increase coverage by 0.00%.
Report is 1 commits behind head on chore_release-7.0.0.
The diff coverage is 70.58%.

Additional details and impacted files

@@                 Coverage Diff                  @@
##           chore_release-7.0.0   #13588   +/-   ##
====================================================
  Coverage                71.32%   71.32%           
====================================================
  Files                     2422     2422           
  Lines                    68141    68145    +4     
  Branches                  7933     7931    -2     
====================================================
+ Hits                     48600    48603    +3     
- Misses                   17685    17687    +2     
+ Partials                  1856     1855    -1     

Flag	Coverage Δ
app	68.96% <76.92%> (+<0.01%)	⬆️
react-api-client	69.12% <50.00%> (-0.18%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
app/src/organisms/FirmwareUpdateModal/index.tsx	82.75% <50.00%> (+4.18%)	⬆️
...c/subsystems/useCurrentAllSubsystemUpdatesQuery.ts	87.50% <50.00%> (-12.50%)	⬇️
...t/src/subsystems/useCurrentSubsystemUpdateQuery.ts	87.50% <50.00%> (-12.50%)	⬇️
app/src/organisms/Devices/PipetteCard/index.tsx	61.29% <100.00%> (ø)
...sms/FirmwareUpdateModal/FirmwareUpdateTakeover.tsx	100.00% <100.00%> (ø)
app/src/organisms/GripperCard/index.tsx	92.59% <100.00%> (-0.27%)	⬇️

[sfoster1]

Tested on a robot with a pipette with an erased application; the app follows along and immediately (well, 5s poll duration) shows that the update is complete even when it was started from the ODD.