Messages queues don't wait for the next batch timeout if a previous one finishes #1690
Description
An earlier change made the message queues continue trying to send messages until the queues are empty (so that drain works). However, because of async code, it's possible that more messages might legitimately fill in that we don't want to send immediately (batching instead of flush). This was caused by:
The visible symptom is that you can set a max number of messages in a batch with a long max timeout, and then do async publishMessage() for more than the max number of messages, but all of them will basically send at once, instead of waiting for the timeout for the second batch. (bug 270113896)