kcc support priority and its allowed selector key list

[luomingmeng]

What type of PR is this?

Features

What this PR does / why we need it:

To enhance the functionality of KCC (Katalyst Custom Configuration), it is necessary to extend its support for multiple node selector keys instead of just one. This is required because in certain scenarios, the node configuration may be differentiated by multiple labels, such as machine type, sub-cluster, physical space, and other attributes.

By allowing the involvement of multiple keys in the selector, there is a higher likelihood of configuration overlap. To address this, we propose introducing a priority system that enables the overriding of lower priority configurations in specific cases, such as during degradation.

[codecov]

Codecov Report

Patch coverage: 54.08% and project coverage change: +0.09% 🎉

Comparison is base (0d40f83) 51.57% compared to head (bbf20e3) 51.66%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #189      +/-   ##
==========================================
+ Coverage   51.57%   51.66%   +0.09%     
==========================================
  Files         430      431       +1     
  Lines       40919    41030     +111     
==========================================
+ Hits        21102    21199      +97     
- Misses      17512    17526      +14     
  Partials     2305     2305              

Flag	Coverage Δ
unittest	51.66% <54.08%> (+0.09%)	⬆️

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

Files Changed	Coverage Δ
pkg/controller/kcc/util/kcct.go	25.33% <0.00%> (-0.83%)	⬇️
pkg/controller/kcc/kcct.go	32.43% <55.55%> (+3.31%)	⬆️
pkg/controller/kcc/kcc.go	55.45% <68.18%> (+0.80%)	⬆️
pkg/util/kcct.go	69.09% <100.00%> (+0.86%)	⬆️

... and 16 files with indirect coverage changes

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