Add a Ready condition type for compatibility with Kubernetes tools and controllers

[cosmic-commit]

Is your feature request related to a problem? Please describe.
The Vault Secrets Operator CRDs (such as VaultStaticSecret, VaultDynamicSecret, etc.) currently define the following condition types:

TypeResourceValidation = "ResourceValidation"
TypeRolloutRestart     = "RolloutRestart"
TypeSecretSynced       = "SecretSynced"
TypeLeaseRenewal       = "LeaseRenewal"
TypeHealthy            = "Healthy"

While these cover key internal states, the CRDs do not expose a Ready condition, which can limit compatibility with external Kubernetes controllers and tools that check for status.conditions[type=Ready].
We use Rancher Fleet for GitOps. Fleet’s dependsOn feature (https://fleet.rancher.io/ref-fleet-yaml) waits for dependent bundles to report a status.conditions[type=Ready, status=True] before continuing with downstream deployments.
Previously, we used External Secrets Operator (ESO), which publishes a Ready condition when a secret is successfully synced. This allowed Fleet to correctly evaluate dependencies and deploy workloads in order.
Describe the solution you'd like
Please consider adding a high-level Ready condition that summarizes the existing detailed conditions.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.