A cherry-picked MR will be tracked as deployed twice
With !22209 (merged) we developed #36130 (closed) to track MR deployments when the commit is cherry-picked.
There is a side effect of this if we deploy disjointly the pick and the merge_commit (which is our use case) that MR will be tracked twice.
We have a uniqueness index on merge_request_id, deployment_id
but we don't take into account the environment.