Currently, When we create a ManagedCluster with a ManifestWork from Cluster Service part and send the ManifestWork through Maestro to the Management Cluster, the ACM will update the ManagedCluster `.spec.managedClusterClientConfigs.url`, but this update cannot be synced back to Cluster Service

We may have two ways, one is we introduce the cluster api url in ManagedCluster status, thus the CS will not need to do any change other than looking in the status, and as an alternative way (see  https://issues.redhat.com/browse/ARO-9544

), we may introduce an annotation (overridespec) on the Cluster Service part,

1. when we send a resource with CS client, the client will wrap the resource to a ManifestWork
2. if the resource has this annotation, the CS client will add a feedback rule (.spec) in the ManifestWork  configs
3. Once the ManifestWork handled by the maestro agent, the maestro agent will sync the resource spec to the ManifestWork status
4. when the CS client receives the status update,  it will unwrap the ManifestWork to get the spec from the status, and replace the current resource spec