When the sub cluster frequently add and delete workload, karmad-agent will update cluster status frequently, that is inconsistent with the configured via the cluster-status-update-frequency args.

What happened:
when cluster status be changed frequently, the karamda-controller-manager deal with the condition of cluster object frequently.

What you expected to happen:
the interval of cluster.status updated by karmad-agent should be inconsistent with the cluster-status-update-frequency (default 10s)

How to reproduce it (as minimally and precisely as possible):

Environment:

• kubernetes version: v1.20.10
• karmada version: v1.9.1