feat(app): ODD protocol detail and protocol setup status for deck configuration

[ncdiehl11]

closes RAUT-667

Overview

The ODD ProtocolSetup page should render the correct module and deck status taking into account module calibration and connection, and now deck configuration. We need to check for the current deck configuration state to ensure the protocol doesn't require hardware where a fixture currently exists, and alert the user of a location conflict if necessary. The status will also render modules and/or fixtures are missing. This hardware status will also be rendered as the chipText on the ProtocolDetails page.

Test Plan

Testing all cases below on a physical Flex

Protocol requires neither modules nor fixtures

• render disabled setup step with text that no hardware is needed

Protocol requires only modules

• connected, and calibrated: setup step is ready and renders number of modules attached
  
• connected and not calibrated: setup step is not ready and renders 'Calibration required'
  
• not connected: setup step is not ready and renders "Missing " or "Missing <#> modules"
  
  
• location conflict with deck configuration: setup step is not ready and renders location conflict
  

Protocol requires only fixtures

• properly configured: setup step is ready and renders number of fixtures attached
  
• location conflict with deck configuration: setup step is not ready and renders location conflict
  
• not configured: setup step is not ready and renders "Missing or "Missing <#> fixtures"
  
  

Protocol requires both modules and fixtures

• location conflict for any modules or fixtures with deck configuration: setup step is not ready and renders location conflict
• fixtures configured but modules missing: setup step is not ready and renders "Missing " or "<#> modules missing"
  
• modules connected but fixtures missing: setup step is not ready and renders "Missing " or "<#> fixtures missing"
  
• fixtures configured and modules connected but module calibrations missing: setup step is not ready and renders "Calibration required"
  
• fixtures not configured and modules not connected: setup step is not ready and renders "Missing hardware"
  
• fixtures configured and modules connected and calibrated: setup step is ready and renders number of fixtures and modules attached
  

Changelog

• add hooks for missing and required protocol hardware to optionally accept a protocol analysis object instead of a protocol ID (when called from ProtocolSetup page rather than ProtocolDetails page)
• change rendered text in Modules and deck setup step depending on conflicting, missing, or un-calibrated hardware
• add a hook for getting the number of unready instruments to render on the instruments setup step
• add keys to translation files
• update tests to look for updated for setup step text

Review requests

@brenthagen as discussed in person

Risk assessment

medium. Main risk lies in the enabling/disabling of the protocol Play button based on new deck configuration considerations

[codecov]

Codecov Report

Merging #13855 (da84a11) into edge (b242919) will decrease coverage by 0.14%.
Report is 22 commits behind head on edge.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             edge   #13855      +/-   ##
==========================================
- Coverage   70.86%   70.72%   -0.14%     
==========================================
  Files        2501     1624     -877     
  Lines       70338    53755   -16583     
  Branches     8600     3775    -4825     
==========================================
- Hits        49844    38020   -11824     
+ Misses      18398    15081    -3317     
+ Partials     2096      654    -1442     

Flag	Coverage Δ
app	43.57% <ø> (-25.31%)	⬇️

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

see 886 files with indirect coverage changes

[jerader]

looking good to far! The main thing I noticed in your i18n strings is you're inconsistent when you use {{count}} vs {{num}}. Since count is associated with the plural usage, it would be good to only use {{count}} when using plural.

[brenthagen]

left a few comments - main one is to make sure we're only making changes to protocol setup status here

[brenthagen]

code makes sense to me, checked a few different states but not all - let's be sure to comment out the isReadyToRun condition before merging

[brenthagen]

LGTM !