without this cleanup, the software integration tests of KVM were stuck
forever because unittest was waiting for the subprocess to stop.

if '-ltinfo', '-ltermcap' or '-lcurses' is set in the linker option,
sqlite3 binary wil link to system libtinfo like this:

slapsoft@tomo-node:~/shared/sqlite3/39068f3749274fa37ab3897081678816/.build/sqlite-autoconf-3370200$ ldd sqlite3
	linux-vdso.so.1 (0x00007fff6dfe6000)
	libreadline.so.8 => /opt/slapgrid/shared/readline/13387ca15e2015da77fab391a268aaa6/lib/libreadline.so.8 (0x00007f4418d7d000)
	libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007f4418d40000)
	libz.so.1 => /opt/slapgrid/shared/zlib/ac3692dceab375c8e6b9c06735e5faf2/lib/libz.so.1 (0x00007f4418d1b000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4418bd7000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4418bd1000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4418bad000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f44189d9000)
	libncurses.so.6 => /opt/slapgrid/shared/ncurses/13a31fd4ae4eaba4a72e42f42c997f1c/lib/libncurses.so.6 (0x00007f441897c000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f4418f5a000)

if libuuid was present on the system, python would link with it in:
lib/python3.9/lib-dynload/_uuid.cpython-39-x86_64-linux-gnu.so

if libtinfo was present on the system, readline would prefer to use it instead of libncurses

This will let a non-shared Theia (for example coming from shacache
binary) to be able to use the shared parts of a machine.

See merge request nexedi/slapos!1409

See merge request nexedi/slapos!1407

See merge request nexedi/slapos!1399

Fix takoever of a theia with initial embedded instance. The issue was
that the promise checking that the embedded instance was successfully
requested relied on files which were not transferred to backup theia.

The location of these files has been changed in order to transfer them;
therefore the old location is still checked for upgrade-compatibility.

Test that takeover of theia with an initial embedded instance succeeds.

See merge request nexedi/slapos!1403

Now each partiton in slapos-sr-testing has its own IPv6 thanks to
ipv6 range, takeover url changes after takoever, so up-to-date
connection parameters need to be fetched before doing a second
takeover.

restart restic after renewing certificate, using the same approach as
software/dufs

Because dufs only reads certificate on startup it does not detect when
the certificate was renewed.

The only thing supported by dufs is to restart, so we use hash-files
options of wrapper recipe to

Resiliency import script had a race condition where the proxy might not
have finished restarting before formatting the partitions, causing the
import script to randomly fail during format because the proxy is down
when format tries to send it updated computer information.

See merge request nexedi/slapos!1406