Move RunNormalizeScorePlugins and ApplyScoreWeights into RunScorePlugins; Also add unit tests for RunScorePlugins.

[liu-cong]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

/kind cleanup

What this PR does / why we need it:
Normalizing scores and applying score weights are details of the Score phase in the framework that the caller (generic_scheduler) doesn't need to care about. With this change, RunScorePlugins method now also runs the normalize and apply score weights logic internally. The change has the following benefits:

• Hides details from outside makes the code easy to use and less error prone
  Previously caller had to call 3 methods in the right order.

• Simplifies the code and unit tests.
  Previously we had to check that score results exists for each plugin in the fear that the score result map could get updated in between the 3 methods. Now the map is an internal data structure and the caller cannot intervene with it during Score.

This is a follow up to a previous comment: One thing we can do to avoid those extra checks and simplify the code in generic_scheduler is to make both RunNormalizeScorePlugins and ApplyWeights private functions of the framework and call them directly at the end of RunScorePlugins.

@hex108, @ahg-g

Which issue(s) this PR fixes:

Contributes to #80272

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @liu-cong. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[alculquicondor]

/ok-to-test

[liu-cong]

/test pull-kubernetes-e2e-gce-device-plugin-gpu

[wgliang]

/lgtm

[ahg-g]

why not keep the functions and just make them local (normalizeScores and applyScoreWeights)?

[liu-cong]

I just found the 3 steps are very similar (parallel execution and receive error) and it looks good to me to put them in the same function (saves a few lines of code). But no particular reason really.

If you like the separately, I can change it.

[ahg-g]

/lgtm
/approve

Thanks Cong

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, liu-cong

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 [ahg-g]

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

[liu-cong]

/test pull-kubernetes-kubemark-e2e-gce-big