ASO should help the user manage CRD storedVersions

[matthchr]

Describe the current behavior
If we deprecate a CRD version that was at one point the storage version (in storedVersions field of CRD status), the user/ASO itself will be unable to update their CRDs. An example of this happened in 2.9.0 with v1api20230202preview of containerservice.

Describe the improvement
We should've supported cleanup up storedVersions via asoctl in the above case, but in the mode where ASO installs its own CRDs we also should just manage this oureslves so that users don't have to fiddle with storedVersions.

We could take a page from Karpenter and do something like this: kubernetes-sigs/karpenter#1689 - or if not a controller (which may not be fully necessary for our case) we could do this checking during or before CRD installation.

An implementation note is that it should probably share logic with asoctl.

Additional context
Add any other context about the suggested improvement.