Disable polling with force update leaves gitrepo in not ready status in 2.9

[mmartin24]

Steps to reproduce.

• Deploy latest rancher 2.9-head
• On local push a gitrepo (which later will be modified) with flag disablePollling: true. I use this one: https://github.com/fleetqa/fleet-qa-examples-public/blob/main/disable-polling/nginx.yaml setting replicas to 2.
• Once repo is deployed change something on the repo. (In the example above, change replicas to 5)
• Click Force Update

Observed behavior:

• Replicas are correctly changed to 5 in deployments but gitrepo remains in Not Ready state and clusters are not ready either (0/1).

Log message on fleet-local description is:

 Message:           NotReady(1) [Cluster fleet-local/local]; deployment.apps disable-polling-nginx-ns/nginx-test-polling [progressing] Deployment does not have minimum availability., Available: 2/5 

Screencast.from.05-11-24.13.32.47.webm

Expected behavior:

• Replicas should be correctly modified and gitrepo should be correctly changed to Active and clusters set to 1/1

Tested on v2.9-023781e52103c45a9bbdf3cb47d60b9336321daa-head and fleet:104.1.1+up0.10.5-rc.2 but happens with a bit earlier versions