fix(api): separate home and backoff steps into separate move groups

[ahiuchingau]

Overview

Since the limit switch and backoff moves are in the same move group, the node will immediately execute the backoff move upon the home completion. This causes a catastrophe if the home request fails: the encoder position will no longer be reporting the correct value and the axis would not be able to home again until powercycled.

We are fixing this by separating the home and the backoff moves into two consecutive move groups, the MoveGroupRunner would now be able to stop the subsystem to perform a backoff move if the home request was not completed by condition.

[codecov]

Codecov Report

Merging #13095 (79922d7) into internal-release_0.13.0-beta-1 (2376f87) will increase coverage by 0.00%.
The diff coverage is n/a.

@@                       Coverage Diff                       @@
##           internal-release_0.13.0-beta-1   #13095   +/-   ##
===============================================================
  Coverage                           72.81%   72.81%           
===============================================================
  Files                                2364     2364           
  Lines                               64472    64447   -25     
  Branches                             7191     7191           
===============================================================
- Hits                                46945    46930   -15     
+ Misses                              15848    15838   -10     
  Partials                             1679     1679           

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

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

Impacted Files	Coverage Δ
...entrons/hardware_control/backends/ot3controller.py	67.37% <ø> (+0.87%)	⬆️
...rc/opentrons/hardware_control/backends/ot3utils.py	91.66% <ø> (ø)