NEO/go doesn't understand what it should do with these parameters and
raises an error in case they are added to the NEO URI [1].

[1] https://lab.nexedi.com/kirr/neo/-/blob/f1a1bb9d/go/neo/client.go#L551-553

'wendelin.core' needs to differentiate between a NEO cluster with SSL
and without SSL from a normalized zurl (e.g. a zurl which doesn't
contain any paths to encryption files). Therefore the 'neo' / 'neos'
scheme difference was introduced in neoppod@bc3e38ea.
This patch introduces this difference in zurl that SlapOS provides for
'wendelin.core' - this essentially fixes a ERP5+WCFS setup that connects
to a NEO cluster with activated SSL.

This reverts commit 0cf70a6e.

NEOgo and NEOpy diverged regarding the NEO zurl format. Due to NEOgo
changes in NEOgo nexedi/slapos@0cf70a6e was necessary.
However in nexedi/neoppod!18 and
nexedi/neoppod!21 a common
zurl format for NEOgo and NEOpy was agreed on. Therefore most changes of
nexedi/slapos@0cf70a6e are no
longer necessary. We still need the difference between 'neo' (without
SSL) and 'neos' (with SSL), but we'll re-introduce this in the next
commit.

This revert keeps the changes made in nexedi/slapos@6fa1d9ae as this is still
needed.

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 !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.