chore: fix pypi deploys of api and shared-data

[sfoster1]

These need to get uploaded to pypi and were not because of some kind of version conflict in api. With a bit of judicious pipenv relocking all is well.

In theory everybody would need to relock but really nobody's running twine so it's fine.

Testing

• do a make deploy-pi to test pypi and see that it runs. i did this already ( opentrons: https://test.pypi.org/project/opentrons/7.0.1a2/ , opentrons_shared_data: https://test.pypi.org/project/opentrons-shared-data/7.0.1a2/ ) which means that if you try to upload it will fail because pypi and test pypi don't allow duplicate files, but as long as it fails because of a 400 error you're good, the issue is twine wouldn't even run

[codecov]

Codecov Report

Merging #13793 (26f90d2) into chore_release-7.0.1 (dfb7acb) will increase coverage by 0.02%.
Report is 2 commits behind head on chore_release-7.0.1.
The diff coverage is n/a.

Additional details and impacted files

@@                   Coverage Diff                   @@
##           chore_release-7.0.1   #13793      +/-   ##
=======================================================
+ Coverage                71.22%   71.25%   +0.02%     
=======================================================
  Files                     2432     1589     -843     
  Lines                    68407    52767   -15640     
  Branches                  8047     3453    -4594     
=======================================================
- Hits                     48724    37598   -11126     
+ Misses                   17793    14634    -3159     
+ Partials                  1890      535    -1355     

Flag	Coverage Δ
app	43.57% <ø> (-25.22%)	⬇️
g-code-testing	96.44% <ø> (ø)
notify-server	89.13% <ø> (ø)
protocol-designer	46.09% <ø> (ø)
step-generation	86.82% <ø> (ø)

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

see 845 files with indirect coverage changes

[SyntaxColoring]

Okey dokey artichokey. 🕺