What happened?

After deploying a composition that includes some Usages, subsequent changes were made to the Usages within the composition and deployed again. Although the Crossplane beta trace indicates that the composition was updated successfully, running kubectl get usages reveals that both the original and new Usages are present in the cluster. This issue is not reflected in the Crossplane beta trace, but it causes interference between the old and new Usages, leading to a failure when attempting to delete the composed resource.

How can we reproduce it?

1. Deploy a composite of a composition including some usages.
2. Make some changes to the composition, resulting in the deletion of some existing Usages, and deploy the updated composition.
3. Run kubectl get usages on the cluster.
4. Observe that the old usage is present.
5. Attempt to delete the composite and encounter blockage due to the old usage still being around.