Improving location support

[OMWalmsley]

Resolves #1970

Locations are where things are stored. Currently we are using a single string in the database to store the location and then frontend application logic on top to create a nested hierarchy. Moving forward it would be ideal to move some of this logic to the backend to prevent locations being generated from stale/deprecated data that has been stored in the frontend.

Features

• Introduces GET \locations endpoint.
  • Which returns a flat list of all locations and a nested list of all locations.
• Introduces HasLocation attribute for all items

Example

An example return from the endpoint is here
{"flat_locations":["Hub1 > Hub2 > Place 1","LHud One","Lab 1 > Shelf 1 > Place A","Lab 4 > Shelf 1","lab1"],"nested_locations":{"Hub1":{"Hub2":{"Place 1":{}}},"LHud One":{},"Lab 1":{"Shelf 1":{"Place A":{}}},"Lab 4":{"Shelf 1":{}},"lab1":{}}}

Testing

Currently three tests have been written to test this endpoint functionality (GET \locations).

Further planned functionality

Implement this into the frontend so that it queries this endpoint instead of using frontend storage.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.06%. Comparing base (6d809c7) to head (c029337).

Additional details and impacted files

@@                         Coverage Diff                          @@
##           ml-evs/bump-pydantic-final-final    #2001      +/-   ##
====================================================================
+ Coverage                             80.02%   80.06%   +0.03%     
====================================================================
  Files                                    83       83              
  Lines                                  7626     7641      +15     
====================================================================
+ Hits                                   6103     6118      +15     
  Misses                                 1523     1523              

Files with missing lines	Coverage Δ
pydatalab/src/pydatalab/models/equipment.py	100.00% <ø> (ø)
pydatalab/src/pydatalab/models/items.py	96.96% <100.00%> (ø)
...datalab/src/pydatalab/models/starting_materials.py	100.00% <100.00%> (ø)
pydatalab/src/pydatalab/models/traits.py	99.04% <100.00%> (+0.02%)	⬆️
pydatalab/src/pydatalab/routes/v0_1/items.py	84.55% <100.00%> (+0.32%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[OMWalmsley]

This PR has been superseeded by #2002