fix(api,app): Block protocol start if the Flex Stacker is not homed or shuttle is missing + home stacker from Desktop app.

[vegano1]

Overview

The Flex stacker Platform might not always be at the homed (gripper) position, which could cause a problem when loading labware on a stacker occupied column 4, since the labware would not be physically where we expected. So let's ensure we can't start the protocol if the relevant stackers are not homed or the shuttle is missing.

Closes: EXEC-1563 EXEC-1572

Test Plan and Hands on Testing

• Make sure the "Play" or "Start Protocol" button is disabled on the ODD and Desktop app if a stacker needs homing or the shuttle is missing.
• Make sure that the "Home Stacker" button is shown in protocol setup for the Desktop App and ODD if the stacker needs to be homed.
• Make sure the "Setup Now" button is shown in protocol setup on the desktop app if the shuttle is missing
• Make sure the "missing-shuttle" status is shown in protocol setup on the ODD if the shuttle is missing

Changelog

• Added 'set_refresh_state' to the FlexStacker module in the API to tell the reader from synchronous methods when to refetch states. This is used when checking if the platform is missing or unknown.
• Added "Home Stacker" button to the protocol setup of the desktop app if the flex stacker needs to home.
• Block protocol start if the flex stacker is not homed or the platform is not extended

Review requests

• Makes sense?

Risk assessment

Low, unreleased.