refactor(protocol-engine): Keep track of failed commands' error recovery types

[SyntaxColoring]

Overview

This goes towards (but does not close) EXEC-346.

Test Plan

We're sufficiently covered by automated tests.

Changelog

• When a command fails, and we choose its recovery type (WAIT_FOR_RECOVERY or FAIL_RUN), store that recovery type for later retrieval.

  We need this for EXEC-346 because when the Python protocol thread sees a failed Protocol Engine command, something needs to tell it whether to raise an exception to immediately fail the run, or wait until an HTTP client issues a resume-from-recovery action.

  That's not done in this PR. It will probably happen in feat(api): Pause when pick_up_tip() errors in a Python protocol #14753.

• As discussed a number of times on the RSS team: Deprecate the old unit testing style of testing CommandView and CommandStore independently. Instead, test them together. We already do this for TipView and TipStore.

  New tests should be added to the new file test_command_state.py. The old test files have been renamed to *old.py but are otherwise left in-place. We should gradually shift things to the new style as we continue to work in this area.

Review requests

None in particular.

Risk assessment

Low.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.24%. Comparing base (3b3c8e4) to head (d30b577).
Report is 3 commits behind head on edge.

Additional details and impacted files

@@           Coverage Diff           @@
##             edge   #14795   +/-   ##
=======================================
  Coverage   67.24%   67.24%           
=======================================
  Files        2495     2495           
  Lines       71325    71325           
  Branches     8961     8961           
=======================================
  Hits        47959    47959           
  Misses      21254    21254           
  Partials     2112     2112           

Flag	Coverage Δ
g-code-testing	92.43% <ø> (ø)

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

Files	Coverage Δ
...pi/src/opentrons/protocol_engine/state/commands.py	99.18% <ø> (ø)

[sfoster1]

Makes sense!