Promote Usage API to Beta

[turkenh]

What problem are you facing?

This is the tracking issue for promoting the Usage API (a.k.a. deletion ordering) to Beta.
With the feature recently merged into the master, we don't have any issues yet, but we will list them here as they appear.

How could Crossplane help solve your problem?

Promote Usage to Beta once we feel confident about it.

### Tasks
- [ ] https://github.com/crossplane/crossplane/issues/5042
- [ ] https://github.com/crossplane/crossplane/issues/5193
- [ ] https://github.com/crossplane/crossplane/issues/6140
- [ ] https://github.com/crossplane/crossplane/issues/5880
- [ ] https://github.com/crossplane/crossplane/issues/5962

[lsviben]

Added an issue based on Community Slack feedback:
#5042

[stevendborrelli]

I need to be able to duplicate the issue, but I have seen instances where due to long running deletions like for DBs or K8s Clusters when having usage dependences via nested XRs, there can be a 15-minute pause between attempted deletes. We should address it before beta.

[bobh66]

In my local implementation of this feature using a kopf operator we see this same problem - it's caused by the garbage collector doing an exponential backoff on the delete retries that maxes out at 1000 seconds (16+ minutes). So when you have something that takes a long time to delete the GC backoff will make it even longer.

I worked around this by explicitly retrying the delete on the "protected" resource when the dependency/usage itself is successfully deleted (the webhook determines that the Usage is no longer required). That seems to speed things up significantly.

I think we discussed this in the original implementation and decided to defer any solution until we had some data on how it was actually working. Explicitly retrying the delete feels risky, but if the resource is already marked for deletion (which it should be) then forcing GC to retry again sooner than it's backoff period should not cause any issues.

[stevendborrelli]

Created issue #5193, this has impacted several users and should be addressed prior to beta graduation.