Tracking: System Update API (phase 2)

[david-crespo]

See #2107 for phase 1 tracking issue and #2100 for most of the code. That work was about setting up the endpoints and the underlying data model without much reference to the actual TUF repo and update artifacts or the update planner. The updates we display in the console is mock data added in #2283 and #2294.

This issue tracks work around replacing that mock data with real data by populating the update tables from the TUF repo and the component version from the actual installed software present in the rack. See #250 for the work on the underlying systems and planner.

Tasks

Preview Give feedback

1. Merge version and version_sort columns #2344
   +0
2. Operator View: Updates - what's the impact of the update? #2040
   Update System api nexus +3
3. [update] Renames to prep for real update work #2834
   Update System +1
4. Define format for TUF master repo containing all system versions #2838
   Update System +1
5. Combine UpdateArtifact and ComponentUpdate, they are the same thing
6. Sort update deployments by time_created desc (requires Sort paginated results by time_created #2343)
7. Nexus datastore: combine update_available_artifact_{upsert,hard_delete_outdated} #766
   Update System cleanup nexus +3