[Feature] Atomic resource propagation for single resource

[NickYadance]

What would you like to be added:

This issue is for tracking the idea of atomic resource propagation in karmada-io/community#170 (comment).

Why is this needed:

The idea is to make a new api or mechanism so that Karmada can propagate resource atomically. By word atomically, it means that resource/propagationpolicy/overridepolicy can be updated simultaneously, instead of one by one. The easiest way to understand this is to think that they are all defined in a single yaml.

This atomic process proves to be useful on paper for single resource propagation to avoid temporary resource status. However, this involves changes to Karmada core API so more specific user cases and suggestions from the community is required. This issue will be used to track ideas and suggestion from Karmada users. Existing user cases and workarounds for this are listed below.

User Case

1. Propagate multiple-part resource to multiple clusters. When new cluster come in, the resource propagation will be delayed until both pp and op updated.

Workaround

1. Manually arrange the update order of pp and op to avoid unnecessary resource propagation.
2. Suspend propagation before updating pp and op, and continue after both are updated.