feat(shared-data): Add backwards compatible pipettes to new pipette configurations

[Laura-Danielle]

Overview

To support fully transitioning to the new pip schema on the app side, we need to include the list of backwards compatible pipettes which is used to detect whether a pipette attached to the robot can be used as a replacement for the pipette specified.

Eventually this key will want to just be a volume range once we support loading pipettes by volume/channels.

I also took the opportunity to remove some migration stuff from the build_json script since we will not need to use that moving forward.

Test Plan

• Throw this on a robot and make sure you can still successfully load supported pipettes in a protocol on a Flex.

[codecov]

Codecov Report

Merging #12514 (07e5229) into edge (85d9161) will increase coverage by 0.08%.
The diff coverage is 10.00%.

@@            Coverage Diff             @@
##             edge   #12514      +/-   ##
==========================================
+ Coverage   73.58%   73.67%   +0.08%     
==========================================
  Files        2255     2261       +6     
  Lines       62142    62277     +135     
  Branches     6514     6581      +67     
==========================================
+ Hits        45729    45883     +154     
+ Misses      14855    14831      -24     
- Partials     1558     1563       +5     

Flag	Coverage Δ
app	72.40% <ø> (+0.12%)	⬆️
notify-server	89.13% <ø> (ø)
protocol-designer	46.34% <ø> (ø)
shared-data	75.35% <10.00%> (+2.05%)	⬆️
step-generation	88.20% <ø> (ø)

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

Impacted Files	Coverage Δ
...s_shared_data/pipette/scripts/build_json_script.py	0.00% <0.00%> (ø)
...pentrons_shared_data/pipette/pipette_definition.py	92.18% <100.00%> (+0.06%)	⬆️

... and 39 files with indirect coverage changes

[sfoster1]

nice

[sfoster1]

With that last commit, works on a flex

[Laura-Danielle]

makes sense to me @sfoster1