related to #835, #1773, #1845

this PR removes finalizer on core resources. Finalizer only complicates reconcile and may lead to dangling resources. Additionally keeping removed resource till the next reconciliation is not needed as no additional cleanup actions are performed. with this change finalizer will be removed from existing core resources and will not be added to new ones, but CR deletion still performs finalizer removal for smooth migration

made controller.disableCRDOwnership flag noop, removed owner reference from cluster wide resources and using selector instead.

In later versions we could keep only finalizer removal for CR and drop other API calls

Summary by cubic

Remove operator-added finalizers from core Kubernetes resources to prevent stuck deletions and simplify reconciliation (addresses #835). Finalizers remain only on CRs; existing core objects have legacy finalizers removed during reconcile, and new ones are created without them.

• Refactors

  • Stop adding finalizers in builders for Services, ServiceAccounts, Deployments, StatefulSets, PVCs, PDBs, VPA/HPA, Ingress/HTTPRoute, ConfigMaps, Secrets, and RBAC.
  • Reconcile now removes legacy finalizers on core objects (mergeMeta updated); finalize paths switch to selector-based orphan cleanup with a remove flag; cluster-wide RBAC cleanup respects the cluster-wide access flag and no longer uses OwnerReferences.
  • Remove CRD ownership helpers and all AsCRDOwner methods; no OwnerReferences or finalizers on cluster-scoped RBAC; controller.disableCRDOwnership is a no-op.
  • Minor updates: VMUser.SecretName -> PrefixedName; small logging and rules ConfigMap cleanups; config and utils tidied (maps.Copy, min); tests, docs, and changelog updated.

• Dependencies

  • Bump KIND_VERSION to v0.31.0.

^{Written for commit c7bed6c. Summary will update on new commits.}