Feature Request: Adjust fight detection logic to accommodate frequent HPA status updates

### Checklist

- [x] I did not find a related open enhancement request.
- [x] I understand that enhancement requests filed in the GitHub repository are by default low priority.
- [x] If this request is time-sensitive, I have submitted a corresponding issue with [GCP support](https://cloud.google.com/support-hub).

### Describe the feature

Config Sync currently triggers a "controller fight" (error KNV2005) when an object is updated more than 5 times per minute. However, some Kubernetes controllers, specifically the Horizontal Pod Autoscaler (HPA) when tracking CPU metrics, can validly update an object's status up to 12 times per minute.

We need to refine the fight detection threshold or logic to prevent these false positives for HPA objects while still maintaining the ability to detect actual management conflicts. This may involve increasing the update frequency allowance or exempting specific controller-managed status fields from the standard heat-decay calculation.

### Importance

_No response_