Introduce StatePreservation to PropagationPolicy API

[RainbowMango]

What type of PR is this?

/kind api-change
/kind feature

What this PR does / why we need it:

This PR introduces StatePreservation to PropagationPolicy which will be used to preserve status in case of application failover.

Which issue(s) this PR fixes:
Part of #5788

Special notes for your reviewer:
This PR focuses on application failover behavior, for the cluster failover, will be included in a separate PR.

Does this PR introduce a user-facing change?:

`API Change`: Introduced `StatePreservation` to `PropagationPolicy`, which will be used to preserve status in case of application failover.

[RainbowMango]

cc @mszacillo
This PR does not include cluster failover. I plan to consider it in a subsequent PR(likely in the next release), as it's more complex and involves changing the default behavior of cluster failover.
Let me know what do you think.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.29%. Comparing base (5c3594f) to head (87ef7d0).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5885      +/-   ##
==========================================
- Coverage   46.29%   46.29%   -0.01%     
==========================================
  Files         663      663              
  Lines       54585    54585              
==========================================
- Hits        25270    25268       -2     
- Misses      27690    27691       +1     
- Partials     1625     1626       +1     

Flag	Coverage Δ
unittests	46.29% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[a7i]

/lgtm

curious, could this not be achieved via a customized interpreter?

[mszacillo]

This PR does not include cluster failover. I plan to consider it in a subsequent PR(likely in the next release), as it's more complex and involves changing the default behavior of cluster failover. Let me know what do you think.

Should be alright. Until then we can probably get around with our own local cluster failover change that would give us the failover flag like we want. Let me know if you need help with the cluster failover part!

[RainbowMango]

/lgtm

curious, could this not be achieved via a customized interpreter?

Probably not, as the data could be grabbed from the status that has been collected to ResourceBinding, and I also made a demo for grabbing the data.

[XiShanYongYe-Chang]

LGTM

[RainbowMango]

Until then we can probably get around with our own local cluster failover change that would give us the failover flag like we want. Let me know if you need help with the cluster failover part!

Absolutely, I'm glad to help. But I need to focus on the application failover part as I hope this could be included in this release.

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: a7i

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
• pkg/apis/OWNERS

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