Geo: Split file_registry into lfs_object_registry and upload_registry
This comes out of #5039.
We already extracted
job_artifact_registry in !4719 (merged). Ideally we would finish the job.
The benefits are similar !4719 (comment 66231375):
- Splitting the types into different tables makes logical sense: Uploads are different than LFS
- Allows for potential optimization by querying for rows > ID, rather than doing a full sweep every time
- Reduces the index sizes: no need to index on
- Ordering of columns is better due to migration, leading to better storage packing on disk