Option to have workflow with single available lock run

# Summary

The multi mutex/semaphore feature has a restriction that only becomes apparent with this feature. Prior to this feature there was only ever one possible mutex or semaphore so in case of highpriority wf and lowpriority wf both wanting it the high one would get it. But in case of high priority wf wanting 2 mutexes (1 which is available but the other taken by some other wf) and different low priority wf only wanting 1 mutex (which is available) the low priority wf is unnecessarily blocked from running even though the high priority can't run anyway (since not ALL of its criteria is met)

see https://github.com/argoproj/argo-workflows/pull/13358#discussion_r1681710287

## Use Cases

This is similar to 'short query acceleration' where small tasks are allowed to get a slice of compute whenever the heavy hitters did not necessarily have enough headroom to run

Start with the multi-mutex/semaphore change and the discussion in pull request #13358, then trace how high- and low-priority workflows are considered when multiple locks are requested. Done means a lower-priority workflow can run when its single available lock is sufficient, even if a higher-priority workflow cannot obtain all of its locks.

Written by the indexing model from the issue text.