[Scheduler] about priority scheduling

[whitewindmills]

What would you like to be added:
The current scheduler only schedules resources in order, that is, the resources triggered first can be scheduled first. They are stored in a first-in-first-out queue. This seems too simplistic at the moment, maybe it's time to introduce priority-based scheduling behavior.

Why is this needed:
In large-scale clusters, scheduling responses can become slow, An example use case is for data science workloads. A user may submit a job that they want to be prioritized above other workloads, but do not wish to affect existing work. The high priority resourceBinding will be scheduled ahead of other queued resourceBindings, as soon as sufficient cluster resources "naturally" become free.

[RainbowMango]

Hi @whitewindmills are you able to join this weeks's community meeting as @wengyao04 and her workmates going to share a proposal about priority and preemption scheduling?

[whitewindmills]

@RainbowMango
I'm not sure if I can attend yet, but I'll try.

[RainbowMango]

Now we have two proposals for this feature:

1. First one at Propose binding priority and preemption #4993
2. Second one at Google Doc