Attachments presented in UI when they don't exist in the Storage

Description

When a customer removed an evidence and then uploaded it again, an issue with the remove evidence logic was removed from S3 storage (it's available on the backup folder only), but there were 2 entries for the same name on the DB, and the app is constructing the URL with the first ID, and that was the "old" one removed.

How to reproduce

1. Attach a file to a Test Run
2. Delete the attachment
3. Upload the same attachment

Actual result/Attachments

In the client case, the second uploaded attachment was triggering the "No such file" error because it was trying to open the previous one that was deleted.

Expected result

The conflict in the database should not be happening as the previous one should be entirely removed from the database.

Version

• 6.12.1