feat(api): remove use of LPC offsets during labware movement

[sanni-t]

Overview

Closes RLAB-237

From hardware testing it has been found that adding LPC offsets during labware movement with gripper makes labware pick ups and drops unreliable. But having the pickUp & drop offsets is useful for fine tuning the default positions of labware pickUp & drop. So this PR removes the use of just LPC offsets from API and engine's labware movement commands.

Helps reduce change diff for RLAB-295.

Test Plan

Just unit tests and linting should suffice since this is removing a functionality that neither science/beta testers not hardware testing is using. Still, a quick test of labware movement on the flex would be helpful in making sure everything still works before making the larger changes of RLAB-295.

Changelog

• removed use_pick_up_location_lpc_offset and use_drop_location_lpc_offset from protocol_context.move_labware args
• removed usePickUpLocationLpcOffset and useDropLocationLpcOffset from moveLabware engine command
• renamed any args/ classes that were called "experimental"
• added a missing sync_client test

Review requests

• It's a very straightforward removal of args & params so should be an easy review

Risk assessment

Low. Just a risk about 'whether the lpc offsets could ever be useful?'. But we can always put them back in if that happens.

[codecov]

Codecov Report

Merging #13144 (f503a71) into edge (fc2ffdb) will increase coverage by 0.47%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             edge   #13144      +/-   ##
==========================================
+ Coverage   72.08%   72.55%   +0.47%     
==========================================
  Files        1530     2390     +860     
  Lines       50741    65933   +15192     
  Branches     3144     7306    +4162     
==========================================
+ Hits        36576    47838   +11262     
- Misses      13657    16350    +2693     
- Partials      508     1745    +1237     

Flag	Coverage Δ
app	71.26% <ø> (+27.32%)	⬆️
g-code-testing	96.44% <ø> (ø)
notify-server	89.13% <ø> (ø)
protocol-designer	47.29% <ø> (ø)
shared-data	78.40% <ø> (-0.95%)	⬇️
step-generation	87.17% <ø> (ø)

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

Impacted Files	Coverage Δ
api/src/opentrons/protocol_api/protocol_context.py	91.66% <ø> (-0.14%)	⬇️
...c/opentrons/protocol_engine/clients/sync_client.py	100.00% <ø> (ø)
api/src/opentrons/protocol_engine/types.py	97.65% <ø> (-0.06%)	⬇️

... and 869 files with indirect coverage changes

[SyntaxColoring]

Code LGTM, thanks! Nice catch on the missing SyncClient test.