fix: add UPDATE operation to initdata injection policy

The policy only fired on Pod/Deployment CREATE, so pods created before
the initdata ConfigMap existed never got the cc_init_data annotation.
Adding UPDATE allows Kyverno to inject the annotation when a Deployment
is updated (e.g. by ArgoCD sync), triggering a rolling restart with
the correct initdata.

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

Author: butler54

charts/all/coco-kyverno-policies/templates/inject-coco-initdata.yaml

@@ -24,6 +24,7 @@ spec:
                 - Pod
               operations:
                 - CREATE
+                - UPDATE
       preconditions:
         all:
           - key: "{{ "{{" }}request.object.spec.runtimeClassName || '' {{ "}}" }}"