TaskRunnerConfigurer behavior change of withThreadCount method #71
Description
In version 3.x, when the TaskRunnerConfigurer is configured using the withThreadCount(n) method, its effect was to create a shared thread pool and distribute n execution permits among all the worker threads collectively.
However, in version 4.x, the behavior of this method seems to have changed: it now appears to create separate thread pools of n threads for each individual worker thread and assigns n execution permits to each individual worker thread.
Is this change in behavior an intentional design change, or is it a bug inadvertently introduced?