Change the scheduler plugins FactoryAdapter function to use context parameter to pass logger

[mengjiao-liu]

What type of PR is this?

/kind feature

What this PR does / why we need it:

• Change the scheduler plugins new function to pass logger parameter
• Migrated pkg/scheduler/framework/plugins/nodevolumelimits to use contextual logging

Which issue(s) this PR fixes:

Part of #91633 (comment)

Special notes for your reviewer:

Follow the suggestion of #116842 (comment), instead of passing the logger using handle.Logger(), we pass the context.
Doing so changes the parameters passed in to initialize New function, and some other plugins parameter will also need to be modified.

// file:  pkg/scheduler/framework/runtime/registry.go

// before
func FactoryAdapter(fts plfeature.Features, withFts PluginFactoryWithFts) PluginFactory {
        return func(plArgs runtime.Object, fh framework.Handle) (framework.Plugin, error) {
                 return withFts(plArgs, fh, fts)

// after
// FactoryAdapter can be used to inject context and feature gates for a plugin that needs
// them when the caller expects the older PluginFactory method.
func FactoryAdapter(ctx context.Context, fts plfeature.Features, withFts PluginFactoryWithFts) PluginFactory {
	return func(plArgs runtime.Object, fh framework.Handle) (framework.Plugin, error) {
		return withFts(ctx, plArgs, fh, fts)
	}
}

Some plugins need to pass context during initialization, and the changes are as follows:

	registry := runtime.Registry{
                ...
		selectorspread.Name:                  selectorspread.New,
		nodevolumelimits.AzureDiskName:       runtime.FactoryAdapter(ctx, fts, nodevolumelimits.NewAzureDisk),
                ...
	}

see ef4ac99#diff-b5d92dd0897babb368df8c1aad9e95c957eca378bd46481d6d8501011f722715 for more details.

see #116884 (comment) for the newest change.

Does this PR introduce a user-facing change?

Migrated the nodevolumelimits scheduler plugin to use [contextual logging](https://k8s.io/docs/concepts/cluster-administration/system-logs/#contextual-logging).

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

- [KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging

/sig instrumentation
/wg structured-logging
/area logging
/sig scheduling

#116842 (comment)
The plugins(volumebinding #116803 ,examples/stateful #116885) can use context after waiting for this PR merge.

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[mengjiao-liu]

/test all

[mengjiao-liu]

/test all
#116842 (comment) Modify PR to pass the context directly instead of handle.Logger() method.

[mengjiao-liu]

/remove-sig node
/remove-sig storage

[mengjiao-liu]

Rebased to resolve conflicts.

[mengjiao-liu]

/retest

[mengjiao-liu]

/test pull-kubernetes-node-e2e-containerd

[alculquicondor]

/lgtm
/approve

Thanks!

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 04b8dcb1b7e657067a9acd906266ffc5414616f8

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, kerthcet, mengjiao-liu

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:

• cmd/kube-scheduler/OWNERS [alculquicondor,kerthcet]
• pkg/scheduler/OWNERS [alculquicondor,kerthcet]
• test/integration/scheduler/OWNERS [alculquicondor,kerthcet]

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

[mengjiao-liu]

/hold cancel

[k8s-ci-robot]

@mengjiao-liu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-unit	a7466f4	link	unknown	/test pull-kubernetes-unit

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[mengjiao-liu]

/test pull-kubernetes-unit