Premature Kubectl Wait Return For Composite Resource Readiness

When waiting for a composite resource to assume the Ready state, kubectl wait may return prematurely. This could imply that the Ready state is briefly set and then revoked.

Example:
kubectl-v1.27.3 wait vault.sec.upbound.io configuration-vault --for=condition=Ready --timeout 5m

After kubectl wait returned, crossplane beta trace vault.sec.upbound.io configuration-vault shows that the resource is not yet ready.

```
NAME SYNCED READY STATUS
Vault/configuration-vault (default) True False Waiting: ...resource claim is waiting for composite resource to become Ready
└─ XVault/configuration-vault-mhtj5 True False Creating: Unready resources: xVaultAuth, xVaultPolicies, and xVaultSecrets
├─ XAuth/configuration-vault-mhtj5-g2cbg True False Creating: Unready resources: generic-endpoint, userpass-auth-backend
│ ├─ Backend/configuration-vault-auth-backend-userpass True True Available
│ └─ Endpoint/configuration-vault-auth-generic-endpoint True False Creating
```

Start by reproducing the kubectl-v1.27.3 wait command for the composite resource, then compare its return point with the crossplane beta trace output shown here. No source file or test is identified; done means establishing why the Ready condition is observed prematurely and adding coverage for the corrected wait behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.