Introduce a mechanism to scheduler to actively trigger rescheduling

[chaosi-zju]

What type of PR is this?

/kind api-change
/kind feature

What this PR does / why we need it:

Introduce a mechanism to scheduler to actively trigger rescheduling

Which issue(s) this PR fixes:

Fixes part of #4840

Special notes for your reviewer:

How to test it：

1. create a deployment and policy like follows:

resource.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: demo-test-1
  labels:
    app: test
spec:
  replicas: 3
  selector:
    matchLabels:
      app: demo-test-1
  template:
    metadata:
      labels:
        app: demo-test-1
    spec:
      terminationGracePeriodSeconds: 0
      containers:
        - image: nginx
          name: demo-test-1
          resources:
            limits:
              cpu: 10m
              memory: 10Mi
---
apiVersion: policy.karmada.io/v1alpha1
kind: PropagationPolicy
metadata:
  name: default-pp
spec:
  placement:
    clusterAffinity:
      clusterNames:
        - member1
        - member2
    replicaScheduling:
      replicaDivisionPreference: Weighted
      replicaSchedulingType: Divided
      weightPreference:
        dynamicWeight: AvailableReplicas
  resourceSelectors:
    - apiVersion: apps/v1
      kind: Deployment
      name: demo-test-1
      namespace: default

2. when first schedule finished, update schedule result in bingding manually, like:

ka patch rb demo-test-1-deployment --type='json' -p '[{"op": "replace", "path": "/spec/clusters", "value": [{"name": "member2", "replicas": 3}]}]'

3. add filed spec.rescheduleTriggeredAt binding manually, like:

ka patch rb demo-test-1-deployment --type='json' -p '[{"op": "replace", "path": "/spec/rescheduleTriggeredAt", "value": "2024-04-18T11:38:15Z"}]'

notes that the timestamp value can set to one second later than current status.lastScheduledTime.

4. check whether reschedule executed by observing whether spec.cluster and status.lastScheduledTime updated.

Does this PR introduce a user-facing change?:

Introduce a mechanism to scheduler to actively trigger rescheduling

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 26.31579% with 56 lines in your changes are missing coverage. Please review.

Project coverage is 52.97%. Comparing base (fdad87e) to head (0372cab).
Report is 14 commits behind head on master.

Files	Patch %	Lines
pkg/scheduler/scheduler.go	10.81%	33 Missing ⚠️
pkg/scheduler/core/division_algorithm.go	0.00%	14 Missing ⚠️
pkg/scheduler/core/assignment.go	46.15%	5 Missing and 2 partials ⚠️
pkg/scheduler/core/common.go	66.66%	1 Missing ⚠️
pkg/scheduler/core/generic_scheduler.go	66.66%	1 Missing ⚠️

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

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4848      +/-   ##
==========================================
- Coverage   53.11%   52.97%   -0.15%     
==========================================
  Files         250      250              
  Lines       20351    20420      +69     
==========================================
+ Hits        10810    10817       +7     
- Misses       8824     8883      +59     
- Partials      717      720       +3     

Flag	Coverage Δ
unittests	52.97% <26.31%> (-0.15%)	⬇️

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.

[chaosi-zju]

ready to review, already tested @RainbowMango

[RainbowMango]

I tend to start with the proposal(#4698).

[RainbowMango]

/assign @XiShanYongYe-Chang

[RainbowMango]

/lgtm

@XiShanYongYe-Chang Do you have any further comments?

[XiShanYongYe-Chang]

/LGTM

[RainbowMango]

/approve

[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