Support "x_unit": unit conversions, ranges and validation

[odeimaiz]

What do these changes do?

BackEnd:

• Entry inputsUnits added to project schema and model: project:workbench:{nodeId}:inputsUnits

FrontEnd:

• Hardcode some units info based on Pint unit library
• Render x_unit in inputs field (updateble): short label (µs, km) in field and long label (microsecond, kilometer) in tooltip
• Render x_unit in outputs field (non updatable): short label (µs, km) in field and long label (microsecond, kilometer) in tooltip
• Users can change the unit prefix by clicking on the unit field
• When the user clicks on the unit field:
  • Prefix is updated
  • Value is updated
  • Field constraints are updated
• Serialize units that differ from the schema in inputsUnits
• Deserialize units coming in inputsUnits
• When serializing a project, inputs are converted back to the unit specified in schema
• When deserializing a project, inputs are converted to the unit specified in inputsUnits
• If the service provides a minimum/maximum value for an input field, they are validated in the frontend.

Inputs from Demo Units service more:

Related issue/s

Related to ITISFoundation/osparc-issues#515

How to test

Checklist

[codecov]

Codecov Report

Merging #2894 (88d53eb) into master (60e462a) will increase coverage by 6.2%.
The diff coverage is 100.0%.

@@           Coverage Diff            @@
##           master   #2894     +/-   ##
========================================
+ Coverage    73.1%   79.3%   +6.2%     
========================================
  Files         551     671    +120     
  Lines       23736   27613   +3877     
  Branches     2626    3223    +597     
========================================
+ Hits        17365   21923   +4558     
+ Misses       5702    4941    -761     
- Partials      669     749     +80     

Flag	Coverage Δ
integrationtests	65.7% <ø> (-0.1%)	⬇️
unittests	75.0% <100.0%> (+7.4%)	⬆️

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

Impacted Files	Coverage Δ
...e_api_server/utils/solver_job_models_converters.py	86.4% <ø> (ø)
.../src/models_library/function_service/demo_units.py	100.0% <100.0%> (ø)
...odels-library/src/models_library/projects_nodes.py	95.5% <100.0%> (ø)
...rvice_datcore_adapter/utils/requests_decorators.py	71.0% <0.0%> (-7.9%)	⬇️
...ore_service_director_v2/utils/dask_client_utils.py	73.4% <0.0%> (-1.3%)	⬇️
...tor_v2/modules/dynamic_sidecar/scheduler/events.py	93.7% <0.0%> (-1.2%)	⬇️
...ector_v2/modules/dynamic_sidecar/scheduler/task.py	86.0% <0.0%> (-0.5%)	⬇️
...ings-library/src/settings_library/utils_service.py	95.0% <0.0%> (ø)
...ice-library/src/servicelib/fastapi/dependencies.py	0.0% <0.0%> (ø)
...ages/models-library/src/models_library/generics.py	91.8% <0.0%> (ø)
... and 208 more

[pcrespov]

I assume that this PR will only introduce units for single-type values i.e. not objects or lists (that comes in another PR?).

[odeimaiz]

I assume that this PR will only introduce units for single-type values i.e. not objects or lists (that comes in another PR?).

Exactly, since the input values do not support objects, I didn't see the point on supporting them in the units. Let's discuss it offline.

[sanderegg]

pair reviewed, great!

[GitHK]

Fine with me, nothing to add.

[KZzizzle]

very nice!!