Double the timing expectations for the queue batching tests

[nolar]

What do these changes do?

Double the timing expectations for the queue-batching tests.

Description

Previously, before #522, the timing allowances were very broad, so the tests passed even if the number of "batching" attempts (and, therefore, timing) were different from expected.

Now, the timing allowances are dynamically & statistically calculated in the environment where it runs, with different overhead for the non-timed code. As a result, the timing allowances for the tests were narrowed to the strictly expected timing of each "batching" cycle plus overhead. As a result, the number of times this "baching" is performed started to matter.

In the queue batching test, there are 2 batches actually expected: one for a batch of events, another one for the EOS token when the watcher finishes. The tests were expecting only 1.

Now, they will expected 2.

This only fixes the CI pipeline and does not affect the users.

Issues/PRs

Issues: #212 #338

Related: a follow-up for #522.

Type of changes

• Bug fix (non-breaking change which fixes an issue)
• Mostly CI/CD automation, contribution experience

Checklist

• The code addresses only the mentioned problem, and this problem only
• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt