koord-scheduler: support NUMA-aware scheduling

[eahydra]

Ⅰ. Describe what this PR does

• Plugin NodeNUMAResource supports scheduling Pods based on NUMA node topology and policies defined on Node or NRT.
• Currently the plugin supports all strategies including BestEffort, Restricted and SingleNUMANode.
• And it is also compatible with the original CPUSet scheduling logic
• But it does not support Pod allocation and preemption from Reservation and Node based on NUMA Node Topology, which I will implement later.
• And it does not support scoring based on the NUMA node topology. I haven't figured out how to implement a new scoring algorithm to be compatible with the original CPUSet scenario, or I can consider scoring only according to the resources of the NUMA Node.

All E2E cases have passed.

Ⅱ. Does this pull request fix one issue?

part of #228

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

V. Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests
• All checks passed in make test

[codecov]

Codecov Report

Patch coverage: 49.11% and project coverage change: -0.50% ⚠️

Comparison is base (8a73b0e) 65.25% compared to head (bf95700) 64.75%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1592      +/-   ##
==========================================
- Coverage   65.25%   64.75%   -0.50%     
==========================================
  Files         359      360       +1     
  Lines       36719    37183     +464     
==========================================
+ Hits        23960    24077     +117     
- Misses      11011    11341     +330     
- Partials     1748     1765      +17     

Flag	Coverage Δ
unittests	64.75% <49.11%> (-0.50%)	⬇️

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

Files Changed	Coverage Δ
...scheduler/plugins/nodenumaresource/cpu_topology.go	53.47% <ø> (-0.33%)	⬇️
...cheduler/plugins/nodenumaresource/topology_hint.go	0.00% <0.00%> (ø)
...duler/plugins/nodenumaresource/resource_manager.go	37.72% <37.72%> (ø)
...duler/plugins/nodenumaresource/topology_options.go	51.85% <51.85%> (ø)
...heduler/plugins/nodenumaresource/plugin_service.go	53.84% <57.77%> (-23.94%)	⬇️
pkg/scheduler/plugins/nodenumaresource/plugin.go	65.64% <65.06%> (+2.03%)	⬆️
...eduler/plugins/nodenumaresource/node_allocation.go	70.21% <70.21%> (ø)
...duler/plugins/nodenumaresource/pod_eventhandler.go	60.22% <70.83%> (-3.07%)	⬇️
...eduler/plugins/nodenumaresource/cpu_accumulator.go	83.21% <77.50%> (+0.43%)	⬆️
.../plugins/nodenumaresource/topology_eventhandler.go	53.22% <93.33%> (-0.63%)	⬇️
... and 2 more

... and 3 files with indirect coverage changes

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

[jasonliu747]

/lgtm

[koordinator-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hormes

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 [hormes]
• test/OWNERS [hormes]

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