Implement notifySpecific by using a worker exclusive thread local
sleepState and pipe.
The sleepState previously waitInflight is no longer a member of IoContext
a thread_local PipeSleepStrategy::SleepState is used instead.
It is safe to use a thread_local object because onNewWorkNotification
is only called by the Owner of the sleepState.
Since others (ANYWHERE, EMPER) must not reap newWorkNotifications from
a workers CQ.

Update the algorithm documentation and other code comments.

Sync tools/check-format of EMPER and Mazstab by using the newer
Mazstab version of the script.

In a running gdb process use:

source tools/gdb/dump_runtime_state.py

to dump the state of all threads, all WSL queues and all worker IoContexts.

Generate a new compile_commands database in compile_commands_wo_subprojects/
without the files in subprojects/.
This new compile_commands database is than consumed by iwyu and clang-tidy.

Co-Authored-By: Florian Schmaus <schmaus@cs.fau.de>
Suggested--By: Florian Schmaus <schmaus@cs.fau.de>

Usage run "docker.sh <your command>" to execute <your command> in the
docker image extracted from .gitlab-ci.yml in the emper root directory

NOTE: seccomp filtering is disabled for now since io_uring_* syscalls
are not working everywhere as expected.

xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value

Meson does only emit a warning if unknown options are passed. In our
case, this is always something we should take care of, because an
option we assumed we configured, had no effect.

See also https://github.com/mesonbuild/meson/pull/8658

Since only newer versions of IWYU_TOOL fail with an exit code, we have
to disable -e around the IWYU_TOOL invocation. Otherwise we would not
print IWYU_LOG.

This required that we backport iwyu_tool.py from
https://github.com/include-what-you-use/include-what-you-use/pull/891
into tools/, which supports --load.

Fixes #8.