Unable to upload same the version of a collection after prior version artifact was deleted

Description

See https://issues.redhat.com/browse/AAH-2580 for larger description (2 separate issues) but this new one we thought would be resolved by now. 

We attempted to delete the collection from the system but that gave a 502 back (see above issue). We then successfully removed the collection version from the repo but it looks like the clean up job did not run as intended so we currently cannot upload the same collection version again as we get a duplicate key error. 

This is a blocker currently due to the nature of issues coming from maintainers/partners in which a deletion will need to occur. While they are far and few between (maybe 3-4 a month), this could potentially cause issues if it persists long enough for partners to miss more than a few version releases. With this, I did not label it as critical but would label it as a blocker. (aka its important to be resolved soon but it is actively not on fire and need a resolution this week) 

<NOTE: if priority is 'blocker' or 'critical', please provide justification as to why>

Key Dependency Versions

<applicable package versions from api root such as pulpcore, pulp_ansible, pulp_container>

Note: Bug filers can grab dependency package versions from the api root which has pulpcore, pulp_ansible, pulp_container, and galaxy-importer. For the c.rh.c the api root is https://console.redhat.com/api/automation-hub/

Steps to Reproduce

Delete an existing collection version specifically from the repository. 

Attempt to upload the same collection version.

Actual Behavior

Get duplicate key/collection already exists

Expected Behavior

collection is uploaded and goes into the staging repository