feat(shared-data): add Pydantic models for liquid class schema

[jbleon95]

Overview

Closes AUTH-834.

This PR follows #16267 and implements the schema as shared data Pydantic models for usage in other parts of the codebase. The models follow the schema in a straightforward matter, the only extra parts that needed to be added were custom validators for the params portion of the different liquid handling properties. If the params are None but enable is set to True, it will raise a validation error.

Test Plan and Hands on Testing

Testing is covered by the unit test added which is able to successfully load the example fixture as the Pydantic model.

Changelog

• Added liquid_class folder to Python section of shared-data
• Added Pydantic representation of schema

Review requests

Mostly suggestions for names of files, models, and definitely descriptions. Most of the descriptions written are pretty simple and more useful suggestions would be appreciated.

Risk assessment

Low, new shared data code that doesn't touch anything else.

[codecov]

Codecov Report

Attention: Patch coverage is 96.89922% with 4 lines in your changes missing coverage. Please review.

Project coverage is 74.72%. Comparing base (5658b8a) to head (cc6f654).
Report is 314 commits behind head on edge.

Files with missing lines	Patch %	Lines
...red_data/liquid_classes/liquid_class_definition.py	96.89%	4 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             edge   #16459       +/-   ##
===========================================
+ Coverage   63.28%   74.72%   +11.44%     
===========================================
  Files         300       42      -258     
  Lines       15786     3118    -12668     
===========================================
- Hits         9990     2330     -7660     
+ Misses       5796      788     -5008     

Flag	Coverage Δ
g-code-testing	?
hardware	?
shared-data	74.72% <96.89%> (+1.39%)	⬆️
system-server	?
update-server	?
usb-bridge	?

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

Files with missing lines	Coverage Δ
...red_data/liquid_classes/liquid_class_definition.py	96.89% <96.89%> (ø)

... and 264 files with indirect coverage changes

[sanni-t]

This is good! I like the strict type checking.
Some minor corrections and suggestions for names and descriptions. And the removal of multi-dispense mix

[sanni-t]

We use coordinates in a number of models. Wonder if it'll be useful clubbing together shared models of shared data. Just a thought

[sanni-t]

The schema calls these 'params' while it's 'arguments' here. I think we should use the same thing for both. Was there a particular reason for calling these 'arguments'?

[jbleon95]

Mostly to avoid confusion with the top level aspirateParams, singleDepenseParams, etc. I'd be open to other ideas as long as they disambiguate them with those.

[sanni-t]

Valid point. How about calling the top-level ones as aspirateProperties or aspirateArguments and have the 'params' from schema be 'params' like DelayParams, TouchTipParams? That keeps the naming consistent with schema and still keeps the two entities separate.

I've been calling them aspirateProperties, dispenseProperties etc in the API side of things.

[sanni-t]

Related to the earlier comment- This feels a bit awkward that the type of delay's params is DelayArguments and not DelayParams

[sanni-t]

Thanks for making the changes! LGTM! 🙌