api: support priority+qos apis.

[tan90github]

Ⅰ. Describe what this PR does

In order to implement priorityQosFilter, it is necessary to implement the priorityQosClass API.

Ⅱ. Does this pull request fix one issue?

part of #2161

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

All modified and coverable lines are covered by tests ✅

Project coverage is 66.04%. Comparing base (ceff9cd) to head (e83cf70).
Report is 17 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2280      +/-   ##
==========================================
- Coverage   66.06%   66.04%   -0.02%     
==========================================
  Files         454      458       +4     
  Lines       53405    53921     +516     
==========================================
+ Hits        35281    35612     +331     
- Misses      15586    15751     +165     
- Partials     2538     2558      +20     

Flag	Coverage Δ
unittests	66.04% <ø> (-0.02%)	⬇️

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.

[songtao98]

/assign @saintube

[saintube]

Batch + LS, Free + LS are acceptable in some scenarios.
e.g. Apps allocate Batch resources to co-locate with the Prod pods, but they'd rather get evicted than suppressed.

For now, it is suggested that check the combinations of the priority classes and QoS classes loosely.

[tan90github]

For priority and qos combinations, we only consider the following valid combinations.

QoS\Priority	koord-prod	koord-mid	koord-batch	koord-free
LSE	✅	❌	❌	❌
LSR	✅	❌	❌	❌
LS	✅	✅	✅	✅
BE	❌	✅	✅	✅

Because koord-system is considered as koord-prod, qosNone is considered as LS, and qosSystem is handled separately.

Related PR #2270