Use the "Construct on first use" idom for UTS Release (aka Linux
version) initialization. The previous implementation was fragle and
could lead to segfaults like

    __s2=0x7fffffffe480 "5.16.10-arch1-1", __s1=<optimized out>)
    at /usr/include/c++/11.2.0/bits/char_traits.h:409
    __n=<optimized out>, __s=0x7fffffffe480 "5.16.10-arch1-1", __d=<optimized out>)
    at /usr/include/c++/11.2.0/bits/basic_string.h:359
    __n=<optimized out>, __s=0x7fffffffe480 "5.16.10-arch1-1", __d=<optimized out>)
    at /usr/include/c++/11.2.0/bits/basic_string.h:354
    __str=..., this=0x7ffff7fbd2a0 <emper::lib::LinuxVersion::globalVersion[abi:cxx11]>)
    at /usr/include/c++/11.2.0/bits/basic_string.h:739
    at ../emper/lib/LinuxVersion.cpp:46
    at /usr/include/c++/11.2.0/ext/new_allocator.h:79

if globalVersion's constructor was not yet called. This is the so
called "static initialization order fiasco" in C++.

While the mutex may not be strictly requires, as we do not call
LinuxVersion's non-argument constructor nor getUtsRelease()
concurrently, it can not hurt to have one.

Make the implementations of the work-stealing queue(s) selectable

See merge request !343

Make subprojects

See merge request !344

io: make max unbounded io worker configurable

See merge request !340

Since Linux 5.15 io_uring can limit the number of iow threads created
using IORING_REGISTER_IOWQ_MAX_WORKERS.

Bump liburing wrap to version 2.1 to use
io_uring_register_iowq_max_workers.

Expose this via the meson variable io_unbounded_iow_max and the
environment variable EMPER_IO_UNBOUNDED_IOW_MAX.

See for an detailed explanation:
https://blog.cloudflare.com/missing-manuals-io_uring-worker-pool

This required to break an include cycle between Fibril and
LockedQueue.

Improve LinuxVersion

See merge request !342

Memory manager

See merge request !339

A Linux version including non-digits, like 5.15.23-gentoo-dist, is
very common and nothing we should warn about.

[Runtime] Prefix EMPER workers names with EMPER

See merge request !341

Also add error handling to uname() call.

Add stack-usage stats

See merge request !338

add Context out of bounds write test

See merge request !336

EMPER's Runtime now installs the SIGSEGV handler that checks if the
segmentation fault was caused by hitting the guard page. If the guard
page was hit, then the handler prints an error message.

Also make ContextOutOfBoundsTest more robust by not creating an
infinite recursion, which may be optmized out by the compiler.

[Emper.hpp] Remove unnecessary 'static' keyword

See merge request !337

Add an SIGSEGV handler to the ContextOutOfBoundsTest to ensure that
the received SIGSEGV is caused by accessing the guard page.

Add emper::printInfo()

See merge request !333

The test is a simple infinite recursion hitting the guard page.
The new guard-page-test-runner skips the test if emper::STACK_GUARD_PAGE
is false.

[Context] Add option for guard page at the bottom of stack

See merge request !335

[meson] fix context_alignas option

See merge request !334

The used variables are named assume_*.
And meson does not support concatenating different variable types using
'+' use string.format instead.

[Context] Make context size configurable

See merge request !331

Extend README and switch to one line per sentence

See merge request !329

Also keep the context size at 64 KiB (there was a comment that
errorneously indicated that the context size is 4 MiB).