Fix customization rule priority

Fleet only applies customizations to the first matching.  This update gives priority to making nginx providers work before applying servicemonitors.  Enabling servicemonitors depends on prometheus already being enabled and setup for it and it's very low priority.

Signed-off-by: scottwilliams <scottwilliams@ucsb.edu>

operator/fleet.yaml

@@ -11,24 +11,6 @@ helm:
     crds: 
       enabled: true
 targetCustomizations:
-  - name: prod
-    helm:
-      values:
-        prometheus:
-          servicemonitor:
-            enabled: true
-    clusterSelector:
-      matchLabels:
-        env: prod
-  - name: rancher
-    helm:
-      values:
-        prometheus:
-          servicemonitor:
-            enabled: true
-    clusterSelector:
-      matchLabels:
-        env: rancher
   - name: gke
     helm:
       values:
@@ -51,4 +33,22 @@ targetCustomizations:
             ACMEHTTP01IngressPathTypeExact: false        
     clusterSelector:
       matchLabels:
-        provider.cattle.io: rke2
+        provider.cattle.io: rke2
+  - name: rancher
+    helm:
+      values:
+        prometheus:
+          servicemonitor:
+            enabled: true
+    clusterSelector:
+      matchLabels:
+        env: rancher
+  - name: prod
+    helm:
+      values:
+        prometheus:
+          servicemonitor:
+            enabled: true
+    clusterSelector:
+      matchLabels:
+        env: prod