Geo: Skip file download if file has been migrated to object storage
For job artifacts, we seem to move them from local file storage to object storage quite frequently, but Geo often seems to schedule downloads without considering this.
Instead of issuing an API request to download the file, should we first:
- Verify that the file is still in local store
- If not, then delete the registry entry? I think this deletion might be handled by another Sidekiq job, so we could skip this, but it seems faster if we just went ahead and pruned the entry rather than update the entry with some "synced" status.