test(e2e): skip config-skyhook glob update step per #245

The `glob update` step in config-skyhook/chainsaw-test.yaml is the
canonical reproducer for issue #245 (Owned ConfigMap can permanently
desync from spec when a stale Status.ConfigUpdates entry drives a
spurious interrupt cycle). The operator gets exactly one good
reconcile window per spec change to satisfy the CM-write gate, and
timing on kind regularly misses it.

The issue itself documents this CI workaround:
"Skip the `glob update` step in config-skyhook/chainsaw-test.yaml
with a # TODO(<this-issue>) comment until the fix lands."

This is unrelated to PR #258's CLI changes; the test flake was
previously masked by other failures in the same file and surfaced
after PR #242 closed the StageInterrupt trap.

Signed-off-by: Alex Yuskauskas <ayuskauskas@nvidia.com>

Author: ayuskauskas

k8s-tests/chainsaw/skyhook/config-skyhook/chainsaw-test.yaml

@@ -385,13 +385,19 @@ spec:
     ## parallel: configmaps are distinct steady-state resources
     - assert:
         file: assert-cm-update-no-interrupt.yaml
-  - name: glob update
-    description: Apply a config update using glob-based package selection and assert it completes
-    try:
-    - apply:
-        file: update-glob.yaml
-    ## parallel: all docs checked simultaneously — the ConfigMap data ("changed via glob")
-    ## acts as a natural discriminator preventing matches against the previous step's state
-    - assert:
-        timeout: 270s
-        file: assert-update-glob.yaml
+  # TODO(#245): re-enable once HandleConfigUpdates CM-write gate is fixed.
+  # The `glob update` step is the canonical reproducer for issue #245
+  # (Owned ConfigMap can permanently desync from spec when a stale
+  # Status.ConfigUpdates entry drives a spurious interrupt cycle). It flakes
+  # in CI because the operator gets exactly one good reconcile window per
+  # spec change to write the owned CM, and timing on kind can miss it.
+  # - name: glob update
+  #   description: Apply a config update using glob-based package selection and assert it completes
+  #   try:
+  #   - apply:
+  #       file: update-glob.yaml
+  #   ## parallel: all docs checked simultaneously — the ConfigMap data ("changed via glob")
+  #   ## acts as a natural discriminator preventing matches against the previous step's state
+  #   - assert:
+  #       timeout: 270s
+  #       file: assert-update-glob.yaml