rook-ceph-cluster: drop allowUnsupported from desired via comparePatch remove

Quoted string value still drifted (string "false" != live). comparePatches
apply to the desired manifest, so removing allowUnsupported there matches the
live CR (which omitempty-strips it), clearing the cephcluster Modified status.

Author: tillo

rook-ceph-cluster/fleet.yaml

@@ -31,15 +31,13 @@ diff:
       operations:
         - {op: remove, path: /spec/cleanupPolicy}
         - {op: remove, path: /spec/healthCheck}
-        # allowUnsupported is the ODD ONE OUT: every other op removes an
-        # operator-ADDED default from live, but the chart RENDERS
-        # allowUnsupported:false while Rook omitempty-strips it from the live CR
-        # (live .spec.cephVersion = {image} only). A `remove` of a key absent
-        # from live errors ("Unable to remove nonexistent key") and voids the
-        # ENTIRE patch (all 14 ops), so the whole CephCluster shows as drift.
-        # Use `add` instead: inject allowUnsupported:false into live during
-        # normalization so it matches the rendered manifest. `add` never fails.
-        - {op: add, path: /spec/cephVersion/allowUnsupported, value: "false"}
+        # allowUnsupported: the chart RENDERS allowUnsupported:false while Rook
+        # omitempty-strips it from the live CR (live .spec.cephVersion = {image}
+        # only). comparePatches apply to the DESIRED manifest, so remove it there
+        # to match live. (An earlier `add value: false` used a bare bool, which
+        # Fleet — whose operations[].value is string-typed — fataled on, stalling
+        # the whole gitjob; quoting it injected the string "false" and still drifted.)
+        - {op: remove, path: /spec/cephVersion/allowUnsupported}
         - {op: remove, path: /spec/crashCollector/disable}
         - {op: remove, path: /spec/dashboard/ssl}
         - {op: remove, path: /spec/mgr/allowMultiplePerNode}