Feature Request: Prevent entire Sync blocking when individual resources fail

### 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

Current Behavior: When a RootSync or RepoSync manages multiple resources, a failure in a single resource (e.g., a validation error or webhook failure) causes the entire Sync operation to enter a blocking state. This prevents all other resources from being synchronized, even if they are completely independent of the problematic resource.

For example, users have observed that a failure in a CloudBuildTrigger resource will prevent an unrelated ArtifactRegistryRepository resource from being applied. The Sync remains in a blocked state until the configuration of the problematic resource is fixed.

Feature Request: The Config Sync control loop should be enhanced to automatically resolve or isolate these errors. The desired behavior is for the system to continue syncing valid, independent resources rather than halting the entire process due to a single resource failure.

### Importance

_No response_