feat(eviction): add cpu system pressure eviction plugin

[WangZzzhe]

What type of PR is this?

Enhancements

What this PR does / why we need it:

• add cpu system pressure eviction plugin, which collects cpu usage and load and verifies if these metrics are overused. It will be enabled in the scenarios where the node does not enable co-location.
• add k8s native QoS sorter and pod owner sorter, which can be enabled through configuration in memory system eviction plugin.
• MetricRing has been moved to util.metric

Which issue(s) this PR fixes:

#492
PR in katalyst-api: kubewharf/katalyst-api#74 go.mod should be updated after api PR merged

[codecov]

Codecov Report

Attention: Patch coverage is 71.05263% with 132 lines in your changes are missing coverage. Please review.

Project coverage is 56.26%. Comparing base (74b648c) to head (4db7acc).
Report is 11 commits behind head on main.

Files	Patch %	Lines
...gent/evictionmanager/plugin/cpu/system_pressure.go	78.82%	43 Missing and 22 partials ⚠️
...s/dynamic/adminqos/eviction/cpu_system_eviction.go	38.35%	45 Missing ⚠️
pkg/util/native/pod_sorter.go	57.69%	8 Missing and 3 partials ⚠️
pkg/agent/evictionmanager/plugin/memory/helper.go	0.00%	4 Missing ⚠️
pkg/util/metric/ring.go	88.23%	2 Missing and 2 partials ⚠️
...ynamicpolicy/cpueviction/strategy/pressure_load.go	75.00%	2 Missing ⚠️
...options/dynamic/adminqos/eviction/eviction_base.go	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #518      +/-   ##
==========================================
+ Coverage   56.06%   56.26%   +0.19%     
==========================================
  Files         534      538       +4     
  Lines       49807    50283     +476     
==========================================
+ Hits        27924    28290     +366     
- Misses      18325    18412      +87     
- Partials     3558     3581      +23     

Flag	Coverage Δ
unittest	56.26% <71.05%> (+0.19%)	⬆️

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

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

[waynepeking348]

1. what's the difference between this eviction plugin and cpu-load && cpu-suppression eviction plugins?
2. why don't we implement this eviction in qrm but in eviction-manager? will it be conflict with qrm hybrid logic?

[WangZzzhe]

1. what's the difference between this eviction plugin and cpu-load && cpu-suppression eviction plugins?
2. why don't we implement this eviction in qrm but in eviction-manager? will it be conflict with qrm hybrid logic?

1. This eviction plugin is supposed to be used in non-colocation scenarios(eg. overcommit), detecting the load of node rather than resource pool and selecting evicted pods by native QoS.
2. Qrm plugins will not be run when colocation is not applied in user's clusters, only eviction plugins will run based on metaServer.
   If colocation is applied, cpu-load and cpu-suppression will be used and this plugin should be disabled. @waynepeking348