Do not block global merges to nodes tagged as busy

To avoid starvation of high priority global bucket merges, we do not consider
these for blocking due to a node being "busy" (usually caused by a full merge
throttler queue).

This is for two reasons:
 1. When an ideal state op is blocked, it is still removed from the internal
    maintenance priority queue. This means a blocked high pri operation will
    not be retried until the next DB pass (at which point the node is likely
    to still be marked as busy when there's heavy merge traffic).
 2. Global bucket merges have high priority and will most likely be allowed
    to enter the merge throttler queues, displacing lower priority merges.

0 files changed, 0 insertions, 0 deletions