refactor(api): use labware pool in stacker engine

[CaseyBatten]

Overview

Make retrieve and store work with the labware pool.

flexStacker/retrieve will load up to three labwares (primary, adapter, and lid) and return all their ids. It will decrement the pool count, and set the stacker addressable area as used.

flexStacker/store will consume up to three labwares (primary, adapter, and lid) from whatever's on the carriage, and return all their ids. It doesn't have parameters, just takes whatever's on the carriage. It will fail if whatever's in the carriage doesn't match what's configured in the labware pool.

This PR only contains engine changes and it makes the protocol API a little unstable. We're still pulling the labware object out of the loaded-labwares core based on what's currently on the module; this will work as long as you've loaded the labware previously into the stacker hopper (the old API we're moving away from) and set the labware pool. Fail to load the labware, and you won't have a core; fail to configure the labware pool, and you'll get an error. The next PR will fix this by making the API properly load a labware object, but it should still work even now.

Test Plan and Hands on Testing

• automated tests and analysis

Changelog

• alter flexStacker/retrieve behavior to use the labware pool and not have parameters for the labware kinds anymore
• alter flexStacker/store to modify the labware pool
• Add batch updates for labware location and storage

Review requests

• retrieve behavior look correct? not too awful to read?
• ditto store?

Risk assessment

Low - Only effects new stacker behavior

Closes EXEC-1214

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 24.76%. Comparing base (f0b21f7) to head (bb32cc8).
Report is 7 commits behind head on edge.

Additional details and impacted files

@@            Coverage Diff             @@
##             edge   #17574      +/-   ##
==========================================
- Coverage   25.65%   24.76%   -0.89%     
==========================================
  Files        2840     2840              
  Lines      218559   218579      +20     
  Branches    17945    17947       +2     
==========================================
- Hits        56067    54131    -1936     
- Misses     162477   164434    +1957     
+ Partials       15       14       -1     

Flag	Coverage Δ
protocol-designer	18.86% <ø> (-0.01%)	⬇️
step-generation	4.37% <ø> (-0.01%)	⬇️

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

see 30 files with indirect coverage changes

[caila-marashaj]

what does this location refer to? The deck location of the stacker where a labware started? Or is it an on-deck location or either one?

[caila-marashaj]

these are stacker-specific offsets and not general labware offsets right?