Remove NormalizeScore plugin set from config API.

[liu-cong]

What type of PR is this?
/kind api-change

What this PR does / why we need it:
NormalizeScore plugin set in the config API is not used by the code. Instead, if user wants to implement NormalizeScore, they should configure ScorePlugin in the config API and implement ScoreWithNormalizePlugin interface.

This API isn't currently in use - the scheduler framework is not fully implemented yet. Therefore changing this API should have little to no impact to users.

More details in issue.

Which issue(s) this PR fixes:

Fixes #80908

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NormalizeScore plugin set is removed from scheduler framework config API. Use ScorePlugin only.

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

Scheduler Framework

/sig scheduling

[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.

[liu-cong]

@bsalamat @ahg-g

[fejta-bot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[ahg-g]

/ok-to-test

[liu-cong]

/test pull-kubernetes-integration

[ahg-g]

/lgtm
/approve

[ahg-g]

/assign @erictune

[liu-cong]

/test pull-kubernetes-integration

[liu-cong]

/test pull-kubernetes-integration

[liu-cong]

/test pull-kubernetes-integration

[liu-cong]

/test pull-kubernetes-integration

[liu-cong]

/test pull-kubernetes-integration

[liu-cong]

/test pull-kubernetes-integration

[Huang-Wei]

FYI @draveness to ensure your ongoing PRs are aligned.

[erictune]

You told me offline that you think the scheduler will ignore an unknown field, in the unlikely case that someone chose to put this property in their config file (even though it is a no-op). Based on that, and the fact it had no effect:
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, erictune, 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/apis/config/OWNERS [ahg-g,erictune]
• staging/src/k8s.io/kube-scheduler/config/OWNERS [erictune]

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

[bsalamat]

You told me offline that you think the scheduler will ignore an unknown field, in the unlikely case that someone chose to put this property in their config file (even though it is a no-op).

That's right. I created a small example that shows this: https://play.golang.org/p/MoYt50z9BPJ

Please also note that we have not released even the alpha version of the config for NormalizeScore plugins. So, it should be fine to change it.

[liu-cong]

/test pull-kubernetes-e2e-gce