Tech Story: UEX orbit data + location sync enhancements

[GitAddRemote]

Tech Story

As a platform engineer, I want UEX orbit data ingested and linked to locations in the sync pipeline so that location hierarchy is accurate and the inventory system can reference orbit context when displaying or filtering locations.

Context

The feature/ISSUE-55 branch includes backend UEX orbit entities, migrations, and location sync adjustments that were identified as out of scope for the org inventory add story and carved out separately.

Acceptance Criteria

• Orbits table and entity defined with correct relations to locations
• Migrations created and reversible for the orbit schema changes
• Location sync updated to ingest orbit data and persist relations
• Location population uses orbit info where applicable
• Existing location sync tests updated; new tests added for orbit ingestion
• Sync behaviour documented (what is pulled, how orbits link to locations)

Technical Elaboration

• Add UexOrbit entity with relation to UexLocation
• Update LocationsSyncService to fetch and persist orbit data alongside location sync
• Update storable locations endpoint if orbit data should be surfaced to the frontend
• Ensure delta sync timestamp tracking covers orbit data

Notes

• This work was carved out of User Story: Add catalog items to organization inventory #55 to keep that story focused on the inventory add UI
• Should be completed before or alongside Tech Story: UEX catalog picker + inventory add plumbing #56 (catalog picker) since location hierarchy affects location selectors