EnqueueAffectedBindings and enqueueAffectedCRBs add schedulerNameFilter

[yanfeng1992]

What type of PR is this?

/kind bug

What this PR does / why we need it:

enqueueAffectedBindings and enqueueAffectedCRBs add schedulerNameFilter

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmada-scheduler`: Fixed an issue that the scheduler does not ignore RB/CRB by scheduler name during enqueuing.

[codecov-commenter]

Codecov Report

Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (3eba2a9) 53.46% compared to head (27971f4) 53.44%.

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

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4139      +/-   ##
==========================================
- Coverage   53.46%   53.44%   -0.03%     
==========================================
  Files         234      234              
  Lines       23279    23287       +8     
==========================================
- Hits        12447    12445       -2     
- Misses      10150    10160      +10     
  Partials      682      682              

Flag	Coverage Δ
unittests	53.44% <0.00%> (-0.03%)	⬇️

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

Files	Coverage Δ
pkg/scheduler/event_handler.go	21.72% <0.00%> (-0.74%)	⬇️

... and 1 file with indirect coverage changes

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

[jwcesign]

/LGTM

Nice works!

[yanfeng1992]

/assign @XiShanYongYe-Chang

[RainbowMango]

@yanfeng1992, just out of curiosity, how did you notice it?

[yanfeng1992]

just out of curiosity, how did you notice it?

Karmada's scheduler currently cannot support concurrency. We are trying to use a new scheduler that can support concurrency in large-scale scenarios. Specifically used to handle some resources that can be scheduled concurrently, such as some resources spread through the non replica duplicate pp, cpp. This problem was discovered because we have two schedulers @RainbowMango

[XiShanYongYe-Chang]

Thanks a lot~
/approve

Can you help cherry-pick it to the previous branch?

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: XiShanYongYe-Chang

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:

• pkg/scheduler/OWNERS [XiShanYongYe-Chang]

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

[XiShanYongYe-Chang]

How about update the release note to:
karmada-scheduler: add schedulerName filter when enqueue affected RB/CRB

[yanfeng1992]

How about update the release note to: karmada-scheduler: add schedulerName filter when enqueue affected RB/CRB

ok done

[chaunceyjiang]

/lgtm