support nodegroup as a plugin

[qiankunli]

nodegroup is the nodes with the same specified label, on the basis of nodegroup, different queues and nodegroups have some relationship about affinity and anti-affinity.

case1: different departments (nlp and recommend) use different nodes (nodegroup1 and nodegroup2), tts uses nodegroup1 first, and nodegroup2 can also be used when resources are insufficient, but recommend can only use nodegroup2.

case2: recommend can use private cloud nodes or public cloud nodes, but tts can only use private cloud nodes because its task takes a long time, which is not easy to release public cloud nodes (for saving money)

configrue example

actions: "reclaim, allocate, backfill, preempt"
tiers:
- plugins:
  - name: priority
  - name: gang
  - name: conformance
- plugins:
  - name: drf
  - name: predicates
  - name: proportion
  - name: nodegroup
    arguments:
      groupantiaffinity.required: 
      groupantiaffinity.preferred:
      groupaffinity.required: nlp = nodegroup1,nodegroup2; recommend=nodegroup2
      groupaffinity.preferred: nlp = nodegroup1
      group.label.name = label1
    enablePredicate: true
    enableNodeOrder: true

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign k82cn
You can assign the PR to them by writing /assign @k82cn in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• pkg/scheduler/OWNERS

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

[william-wang]

It's an interesting and common scenario. We ever planed to enhance queue ability to allow configuring policy to filter/select nodegroup which contains a specified type of node :)

[k82cn]

@qiankunli , can we have a design doc for this feature? I have several comments on the behaviour of this feature :)