Dynamically adjustable queue_sizes for thread pools can in general be a useful feature for users to tune depending on their cluster utilization. However, as queue_size tends to Integer.MAX_VALUE, the value of this turns negative. So perhaps we should set a upper bound on queue_size beyond which it can not be set?

Relates #11511, relates #14367 (cf. comment from @dakrone)