test(shared-data): add pressFit pickUpTipConfigurations validation test

[sanni-t]

Overview

I started working towards RSS-496 and as I was updating the definitions to use configsByTipCount, I realized that that schema was more prone to human errors and was too verbose. Even though the current schema looks a bit redundant with three properties keyed by tip count, having a property written as:

currentByTipCount: {"1": 0.1, "2": 0.2, "3": 0.3....}

as opposed to

configByTipCount: { "1": { "current": 0.1, "speed": 12, "distance": 22}, "2": {.....}}

is much more readable, easy to peruse at a quick glance and less prone to human errors because you can spot an anomaly in the pattern right away.

Now the present and easily readable schema still has the problem of tip count keys being missed or out of sync. So this PR adds a test that scans all pipette definitions to verify that each definition has identical keys for speedByTipCount, distanceByTipCount & currentByTipCount.

Test Plan

Checked that removing a key from any definition raises error in the added test.

Review requests

Any opposition to not changing the schema?

Risk assessment

None. Just a test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.71%. Comparing base (4c75aaf) to head (c4d1369).
Report is 2 commits behind head on edge.

Additional details and impacted files

@@           Coverage Diff           @@
##             edge   #14587   +/-   ##
=======================================
  Coverage   67.71%   67.71%           
=======================================
  Files        2510     2510           
  Lines       72245    72245           
  Branches     9287     9287           
=======================================
  Hits        48921    48921           
  Misses      21096    21096           
  Partials     2228     2228           

Flag	Coverage Δ
app	64.68% <ø> (ø)
protocol-designer	37.90% <ø> (ø)
shared-data	75.24% <ø> (ø)
step-generation	86.88% <ø> (ø)

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

[SyntaxColoring]

Cool, TY!