Closes RQA-3608, RQA-3609, RQA-3611, RQA-3613, RQA-3610, RQA-3612, and RQA-3615

Closes RABR-671, RQA-3213, and RQA-3595

…to boot-up. (#16882)

…6875)

#16870 but for chore_release-8.2.0

…16884)

Closes RQA-3583

Currently, the app inspects an errorType on a failed drop tip command to determine whether to throw the special case "home the gantry" error modal. Recently, the error type changed for failed update estimator commands, so the special modal was broken. Instead of special-casing the errorType for failed estimator commands, let's just assume that any failed estimator command is caused by an unknown position error and pop the special modal.

Note that this also handles any error in the same manner with a "MustHomeError" errorType, too.

Closes RQA-3581

)

fix RQA-3482

# Overview

Known issue for downgrading below 8.2 with a plate reader attached.

## Test Plan and Hands on Testing

Check in next alpha.

## Changelog

Single bullet in API release notes.

## Review requests

- Does this capture the issue properly? Is there a related app-side
issue?
- Do we need to mention the problem of downgrading a robot _on the same
network_ as a plate reader?

## Risk assessment

nil

…recovery (#16893)

Closes RQA-3614

# Overview

Prettier (or whatever runs in our JS lint action) demands a newline
after a markdown header. OK.

## Test Plan and Hands on Testing

Pass automated tests plz.

## Changelog

`\n`

## Review requests

Forgive this shameful and time-wasting PR.

## Risk assessment

none

…id_auto_seal_lid to release (#16903)

Covers RABR-669
Adds compatibility between `biorad_96_wellplate_200ul_pcr` and `opentrons_tough_pcr_auto_sealing_lid` with stacking z offset

…al place (#16919)

Covers EXEC-1019
Ensure the plate reader values are truncated to the third decimal place after being read during a protocol.

Closes RQA-3642, RQA-3632, RQA-3627, and RQA-3629

Closes RABR-672

Closes RQA-3645

Recent gripper firmware changes add new degrees of G axis "home" state, and this ultimately causes the unsafe/ungripLabware command to fail, since a successful completion of the ungrip does not set the HOME flag. Because we ultimately want to ungrip the labware AND home the gripper G axis, let's use a parameterized home command instead.

* fix(components): fix unit text wrap-issue

…losed (#16941)

Covers RABR-674
Raises  an error during analysis when the plate reader lid is not closed and a read is attempted.

…#16954)

Closes RQA-3643

Because drop tip flows is no longer deterministic, we shouldn't show the progress bar and step counter.

…e recovery policies during a run (#16950)

Closes RQA-3670

We need to support the client ignoring several different classes of errors in a single run, which means the app needs to know the current recovery policy and be able to modify. This PR adds the necessary infrastructure to support that.

Co-authored-by: Max Marrone <max@opentrons.com>

fix RQA-3570, RQA-3572, RQA-3573, RQA-3633, RQA-3634

Conflicts:

api/src/opentrons/protocol_engine/commands/absorbance_reader/read.py:
Conflict in error message wording between PR #16941 in release and PR #16920 in edge. I took the one in release because the one in edge was an outdated cherry pick.

app/src/organisms/Desktop/Devices/ProtocolRun/ProtocolRunHeader/RunHeaderModalContainer/hooks/useRunHeaderDropTip.ts:
Just import statements.

app/src/organisms/DropTipWizardFlows/hooks/useTipAttachmentStatus/getPipettesWithTipAttached.ts:
Release removed `cursor: null` and `includeFixitCommands: null` from some network requests, leaving those fields unspecified instead (PR ##16893). Edge deleted this whole file in favor of a different one (PR #16904). I removed `cursor: null` from the new file; `includeFixitCommands: null` was already removed.