Karmada should rescheduled when a new cluster is joined

[duanmengkk]

What would you like to be added:
when I apply a propagationPolicy and has a cluster haven't joined,karmada will generate a resourcebinding not include the cluster. When this cluster has joined,the resourcebinding will not regenerated, and will not rescheduled. This makes users must delete propagationPolicy and resourcebinding manually and recreate them so the new joined cluster will participate in scheduling.

Why is this needed:
I think it will enhance the userexperience,more than one of us has had the same problem. Whether the step of joining a cluster must before creating a propagaPolicy.

[dddddai]

Related to #829

[huone1]

in some scenarios，user don't hope to reschedule when adding a new cluster， So is it necessary to add a field in propagation policy to specify whether to trigger the rescheduling

[huone1]

it is considered with the issue #1640

[RainbowMango]

/close
in favor of #2301

[karmada-bot]

@RainbowMango: Closing this issue.

In response to this:

/close
in favor of #2301

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.