Lock resource requests should not be able to skip the line when different label quantities are used #224

Hi,

I would like to utilize the label with the quantity feature like this:

• Light jobs allocate 1 resource by label.
• Heavy jobs allocate all resources of that label.

My expectation is that the order of lock requests behave like a queue:
so when a heavy job requests all resources of that label no other light job will be able to lock such a resource in the meantime, basically no other job should be able to skip the line.

The current implementation feels like a bug to me, as when there are all the time light jobs running, the heavy job will never be able to allocate all the resources by label and as such never be able to go on.

I also played around inversePrecedence, but it did not help with my requirement.

Do I miss something here?

Thanks,
Maik