feat(hardware): add progress output to subsystem firmware update process

[pmoegenburg]

Overview

Add progress reporting to robot microcontroller/subsystem firmware update process. Reporting takes the form (nodeid: (macro_status, micro_status)) for each nodeid being updated, where macro_status is one of (queued, updating, done) and micro_status is a float from 0 to 1 during the updating macro_status.

Test Plan

• Ensure json dictionary passed into update_fws.py script populates update_details dictionary
• Ensure passing in a json dictionary for all nodeids to update_fws.py script logs progress reports for all nodeids from queued to updating to done macro phases and from 0 to 1 micro_status during updating macro phase

Changelog

• Added progress reporting to robot subsystem firmware update process

Review requests

Risk assessment

Low. This builds off of the existing and proven updating process with proven software components.

[codecov]

Codecov Report

Merging #12059 (4de20d8) into edge (7000f23) will increase coverage by 0.57%.
The diff coverage is 78.08%.

@@            Coverage Diff             @@
##             edge   #12059      +/-   ##
==========================================
+ Coverage   74.19%   74.76%   +0.57%     
==========================================
  Files        2223     2176      -47     
  Lines       60956    59765    -1191     
  Branches     6514     6342     -172     
==========================================
- Hits        45225    44684     -541     
+ Misses      14201    13571     -630     
+ Partials     1530     1510      -20     

Flag	Coverage Δ
hardware	57.41% <78.08%> (+0.12%)	⬆️
notify-server	89.13% <ø> (ø)

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

Impacted Files	Coverage Δ
...entrons/hardware_control/backends/ot3controller.py	64.63% <ø> (ø)
hardware/opentrons_hardware/scripts/update_fw.py	0.00% <0.00%> (ø)
hardware/opentrons_hardware/scripts/update_fws.py	0.00% <0.00%> (ø)
hardware/opentrons_hardware/firmware_update/run.py	94.33% <93.33%> (-5.67%)	⬇️
...are/opentrons_hardware/firmware_update/__init__.py	100.00% <100.00%> (ø)
...e/opentrons_hardware/firmware_update/downloader.py	100.00% <100.00%> (ø)
...rdware/opentrons_hardware/firmware_update/types.py	100.00% <100.00%> (ø)
...e/hardware_control/motion_planning/move_manager.py	89.36% <0.00%> (-4.26%)	⬇️
...are/hardware_control/motion_planning/move_utils.py	91.54% <0.00%> (-1.50%)	⬇️
... and 48 more

[sfoster1]

This is looking really solid to me at this point. @vegano1 how does this mesh with #12059 ?

[vegano1]

This is looking really good, will need to adjust a bit to merge in with my work but not too bad.
Once the merge conflict is fixed, this should be good to go.

[sfoster1]

Looks good, tested on machine!