monitoring: quitar last-applied-configuration de los manifiestos propios

Basura del volcado con kubectl get -o yaml. Al estar versionada se muerde la
cola: ArgoCD la aplica, k8s genera una nueva que ya incluye el tracking-id, y
git y cluster no coinciden nunca -> los 4 recursos se quedaban OutOfSync para
siempre. Verificado que el resto del manifiesto queda byte a byte igual.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

monitoring/ingress-uptime-kuma.yaml

@@ -3,9 +3,6 @@ kind: Ingress
 metadata:
   annotations:
     cert-manager.io/cluster-issuer: letsencrypt-prod
-    kubectl.kubernetes.io/last-applied-configuration: '{"apiVersion":"networking.k8s.io/v1","kind":"Ingress","metadata":{"annotations":{"cert-manager.io/cluster-issuer":"letsencrypt-prod","traefik.ingress.kubernetes.io/router.entrypoints":"websecure"},"name":"uptime-kuma","namespace":"monitoring"},"spec":{"ingressClassName":"traefik","rules":[{"host":"status.chemavx.xyz","http":{"paths":[{"backend":{"service":{"name":"uptime-kuma","port":{"number":3001}}},"path":"/","pathType":"Prefix"}]}}],"tls":[{"hosts":["status.chemavx.xyz"],"secretName":"uptime-kuma-tls"}]}}
-
-      '
     traefik.ingress.kubernetes.io/router.entrypoints: websecure
   name: uptime-kuma
   namespace: monitoring