Geo - Ensure that upload deletions are communicated to the secondary

What does this MR do?

When an uploaded file is deleted on the Geo primary, generate a upload_deleted_event. The Geo secondary can then remove the entry form the file_registry table in the Geo tracking database.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

The file_registry table on the secondary falls out of sync with what's actually stored in the uploads table.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• [-] Changelog entry added, if necessary
• [-] Documentation created/updated
• [-] API support added
• Tests added for this feature/bug
• Review
  • [-] Has been reviewed by UX
  • [-] Has been reviewed by Frontend
  • Has been reviewed by Backend
  • [-] Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• [-] Internationalization required/considered
• [-] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan

What are the relevant issue numbers?

Closes #2103 (closed)