use ClusterCacheSyncTimeout for resources on fed control plane as well

[lxtywypc]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Now, the default timeout for waiting cache syncing in controller-runtime is 2 minutes. If we have a lot resources on the fed control plane, the default timeout might be reached and the process would return with an error like:

E0801 06:15:22.538099       1 controllermanager.go:154] controller manager exits unexpectedly: [failed to wait for build-resource-informers for work caches to sync: timed out waiting for cache to be synced, failed waiting for all runnables to end within grace period of 30s: context deadline exceeded

And the karmada-controller-manager would be hard to restart successfully.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:
The log printed above is from karmada-controller-manager v1.3.1, but it still exists in the latest version.

Does this PR introduce a user-facing change?:

`karmada-controller-manager`: The `--cluster-cache-sync-timeout` flag is now used to specify the sync timeout of the control plane cache in addition to the member cluster's cache. The default value has been increased to 2 minutes.

[RainbowMango]

Nice, 100% agree that we need to use the same configuration for informers inside of a controller.

[RainbowMango]

/lgtm
/approve

Thanks @lxtywypc .

I updated the release notes a little bit by the way.

I also revisited the #1112, thanks @snowplayfire for introducing the flag. It means a lot to Karmada's scalability.

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[liangyuanpeng]

It's useful , let me cherry pick it to 1.6

[RainbowMango]

We don't usually cherry-pick features, but considering the severity of this issue(and the fact that you have done it #3880 :)), I'm ok with it.