Remove duplicate releases from database

[mlqn]

Description

There was previously a bug that allowed the creation of multiple releases with the same tag name (e.g., https://altinn.slack.com/archives/C02EJ9HKQA3/p1734509976676659). This issue has been resolved in the backend, but duplicate releases remain in the database.

I suggest :

1. Creating a composite key based on tagName, org and app with a condition based on the buildStatus
2. Cleaning up the database by removing duplicate tag names to prevent confusion and potential side effects, like this one:

duplicated-tag-names.mov