[question] ClusterColocationProfile是否考虑支持priority和只匹配一次？

[j4ckstraw]

What happened:
我们在内部灰度koordinator方案，针对不同的作业预制了多个ClusterColocationProfile，通过命名空间级别来灰度。
但是命名空间对于业务来说可能过大了，需要更精细的灰度方案，所以定制了多个ClusterColocationProfile，但是发现不同的ClusterColocationProfile会相互覆盖，从代码看也是支持匹配多个profile的，想了解一下如此设计的背景和目的。

What you expected to happen:
希望增加优先级支持和只匹配一次的能力。

Environment:

• Koordinator version: - v1.3.0
• Kubernetes version (use kubectl version): v1.21.3
• docker/containerd version: containerd 1.5.0
• OS (e.g: cat /etc/os-release): Ubuntu 20.04.4 LTS
• Kernel (e.g. uname -a): Linux 5.10.112-11.al8.x86_64 ✨ Add NodeMetric API #1 SMP Tue May 24 16:05:50 CST 2022 x86_64 x86_64 x86_64 GNU/Linux

Anything else we need to know:

[j4ckstraw]

#1873

[stale]

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close
  Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Reopen this PR with /reopen
  Thank you for your contributions.