argocd: eliminar kyverno

Sin ninguna ClusterPolicy/Policy definida (0 CRs): no aportaba nada y consumia
4 pods + 22 CRDs. Ademas su sync fallaba de forma permanente porque los CRDs
superan el limite de 262144 bytes en metadata.annotations al aplicarse
client-side.

argocd/applications/kyverno.yaml

@@ -1,40 +0,0 @@
-apiVersion: argoproj.io/v1alpha1
-kind: Application
-metadata:
-  name: kyverno
-  namespace: argocd
-spec:
-  project: default
-  source:
-    repoURL: https://kyverno.github.io/kyverno/
-    chart: kyverno
-    targetRevision: 3.7.2
-    helm:
-      releaseName: kyverno
-  destination:
-    server: https://kubernetes.default.svc
-    namespace: kyverno
-  ignoreDifferences:
-  - group: admissionregistration.k8s.io
-    kind: MutatingWebhookConfiguration
-    jqPathExpressions:
-    - .webhooks[].clientConfig.caBundle
-  - group: admissionregistration.k8s.io
-    kind: ValidatingWebhookConfiguration
-    jqPathExpressions:
-    - .webhooks[].clientConfig.caBundle
-  - group: apiextensions.k8s.io
-    kind: CustomResourceDefinition
-    jqPathExpressions:
-    - .spec.conversion.webhook.clientConfig.caBundle
-  syncPolicy:
-    syncOptions:
-    - CreateNamespace=true
-    - ServerSideApply=true
-    - SkipDryRunOnMissingResource=true
-    - RespectIgnoreDifferences=true
-    # Los CRDs de kyverno superan el limite de 262144 bytes de
-    # metadata.annotations al aplicarlos client-side (last-applied-configuration),
-    # y el sync fallaba con "Too long". Replace=true evita el patch incremental.
-    # Seguro aqui: no hay ninguna ClusterPolicy/Policy definida (0 CRs que perder).
-    - Replace=true