App: User shouldn't be able to calibrate/run if attached pipettes are incompatible with protocol

[mcous]

overview

Currently, if the user simulates a protocol on the robot and the protocol spec's pipettes that are incompatible with the currently attached pipettes, neither the app nor the API prevents the user from proceeding to calibration and then run.

In a well-behaved system, this would be the job of the API to block this behavior, but the entanglement of the RPC API prevents us from doing this properly at this time.

As a stop-gap until the RPC API is replaced, the app should keep the user at the file info page (i.e. disable the calibration and run navigation tabs) if the app detects that the session (protocol simulation) pipettes do not match the attached pipettes (GET /pipettes)

related issues

• Pipette Gen2: Alert User in Modal if Pipette Mismatched #3598
• Pipette swapping is available during protocol simulation, but does not function correctly #2020

current behavior

User is able to calibrate pipettes / labware with incorrect pipettes and proceed to run

This behavior is a holdover from when we weren't comfortable blocking users with "incompatible" pipettes because a non-trivial number of pipettes were leaving the factory without their provisioning process being properly completed. This factory process issue was solved a long time ago.

acceptance criteria

If the robot's attached pipettes are incompatible with the pipettes spec'd in the protocol:

• "Calibrate" nav button is disabled with a tooltip
  • "Please attach the correct pipettes before calibrating your equipment" or similar
• "Run" nav button is disabled with a tooltip
  • "Please attach the correct pipettes before running your protocol" or similar

Note: Disabling the top-level nav button is a lot more straightforward than enabling the page and disabling individual control elements, due to the same entanglement concerns that are leading us to deal with this in the app in the first place.

open questions

• Do we block the flows by either:
  1. Disabling the top-level nav button with a tooltip?
  2. Enabling the page but disabling
• After a pipette swap, does the protocol need to be re-simulated?
  • Ping @Opentrons/py

[sfoster1]

Closed by #4185