Logs for the whole process shall be formatted in the same way, so define it
once in global section.

Long request lines result with truncated logs, which leads to impossibility to
debug cluster.

Maximize the log lines emitted by haproxy, and follow up this withing
accompanying rsyslogd.

Allow very long, but still much smaller, URI logging.

Compiling libuuid was failing with the following error:

```c
libuuid/src/gen_uuid.c: In function 'uuid_generate_time_generic':
libuuid/src/gen_uuid.c:536:33: error: initializer element is not constant
  THREAD_LOCAL int  cache_size = cs_min;
```

The error was previously detected, and a fix was provided in
52abdf6a , where the GCC minimum version
was increased to 8 (GCC version 8 supports using const-declared
variables as constant expressions in some cases).

Unfortunately, the solution did not work as the `min_version` field of
the `[gcc]` section was being overwritten by its value in
`component/defaults.cfg`.
This is because `util-linux` (where libuuid config is located) is a
transient dependence of `defaults.cfg` through `python3`.

Luckily, the error is already [patched upstream](https://github.com/util-linux/util-linux/commit/07e5c29d501c19e7af84fecb5915e0f9f94cb49f)
in version 2.40.1, so we can just upgrade the library to the latest
version instead (2.40.2), which we do here.

As part of the upgrade we disable the new tools added to the package, as
we do not use them: liblastlog2, pam-lastlog2 and exch.
Otherwise the compilation would fail with the following message:

```
configure: error: liblastlog2 selected, but required sqlite3 library not available
```

See merge request nexedi/slapos!1609

We can't use key of type dss anymore.

This is a fixup of aae4a7c0.

We can't generate key of type dsa anymore.

This is a fixup of aae4a7c0.

This reverts commit 5f4833c0.

It will solve a compilation error in libuuid

patch for arbitrary code execution due to heap corruption in `git_index_add`

see: https://github.com/libgit2/libgit2/security/advisories/GHSA-j2v7-4f6v-gpg8
https://security-tracker.debian.org/tracker/CVE-2024-24577

Commit de5e381d broke build of
MariaDB >= 10.5. There were warnings about that with 10.4.

Since openssl 3.0, Config.pm is lauched with shebang "/usr/bin/env perl"
so perl from slapos must be in the PATH.