…tor to avoid deadlocks.

In a multiprocessing.pool, if a process terminates in a non-clean fashion
(for example, due to OOM or a segmentation fault), the pool will silently
replace said process, but the work that the process was supposed to do
will never be done, causing pylint to hang indefinitely.
The concurrent.futures.ProcessPoolExecutor will raise a
BrokenProcessPool exception in that case, avoiding the hang.

…esn't

lead to a deadlock.

…mscripten and WASI.

…ssing for single process fallback.

Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>

for more information, see https://pre-commit.ci