[backport v2.9] Fleet controller and agent update status field too often

[rancherbot]

This is a backport issue for #3004, automatically created via GitHub Actions workflow initiated by @aruiz14

Original issue body:

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I've observed an abnormal number of status updates in some BundleDeployments objects.
While comparing them, I noticed that both Fleet's agent and controller are fighting to update the same field:

@@ -314,6 +314,19 @@
       fieldsType: FieldsV1
       fieldsV1:
         f:status:
+          f:appliedDeploymentID: {}
+          f:nonModified: {}
+          f:ready: {}
+          f:release: {}
+          f:resources: {}
+      manager: fleetagent
+      operation: Update
+      subresource: status
+      time: "2024-10-23T06:17:26Z"
+    - apiVersion: fleet.cattle.io/v1alpha1
+      fieldsType: FieldsV1
+      fieldsV1:
+        f:status:
           .: {}
           f:conditions: {}
           f:display:
@@ -321,27 +334,14 @@
             f:deployed: {}
             f:monitored: {}
             f:state: {}
+          f:syncGeneration: {}
       manager: fleetcontroller
       operation: Update
       subresource: status
-      time: "2024-10-23T06:17:06Z"
-    - apiVersion: fleet.cattle.io/v1alpha1
-      fieldsType: FieldsV1
-      fieldsV1:
-        f:status:
-          f:appliedDeploymentID: {}
-          f:nonModified: {}
-          f:ready: {}
-          f:release: {}
-          f:resources: {}
-          f:syncGeneration: {}
-      manager: fleetagent
-      operation: Update
-      subresource: status
-      time: "2024-10-23T06:17:26Z"
+      time: "2024-10-23T06:17:30Z"

Expected Behavior

fleetcontroller should respect the existing value in the status.

Steps To Reproduce

No response

Environment

- Fleet Version: 0.10.2

Logs

No response

Anything else?

No response