Simplify the compilation to default cmmi

Removed already incorporated patch.

Keep old version and use it with software which needs it.

Patch has been adapted to the new version.

Relax Via string and define it once in caddy-frontend.

Now that slapos.core on python2 can use softwares on python3, we no
longer need to test for python2

when using golang 1.17 build fail with errors like:

    github.com/jacobsa/fuse/internal/buffer.memclr: relocation target runtime.memclrNoHeapPointers not defined for ABI0 (but is defined for ABIInternal)

Update to wendelin.core 2, which reached its alpha state.

Even though it is wendelin.core 2, it continues to work by default in
wendelin.core 1 mode with providing the same stability guarantees as
before. This mode works with all ZODB4, ZODB4-wc2 and ZODB5. However
every Zope has its own private cache for ZBigFile data which wastes RAM,
prevents us to use as many Zopes as there are CPU cores, and potentially
leads to OOM issues where one Zope tend to allocate whole memory while
other Zopes cannot allocate even a single page. This mode, as well as
previous Wendelin.core 1, is also subject to data-corruption that can
happen on ZBigFile's BTree topology change:

wendelin.core@8c32c9f6

WCFS mode - that is what wendelin.core 2 actually provides over
wendelin.core 1 - is currently opt-in. When used in "WCFS mode", all
Zopes share cache for ZBigFile data and there should be no data
corruption. This mode works with both ZODB4-wc2 and ZODB5, but not with
plain ZODB4. The way to opt-in into this mode for a software-release is
to set `erp5-defaults:wcfs-enable-default = true`, like SlapOS Master
currently does:

    # SlapOS Master needs to use Wendelin.core 2.
    # Wendelin.core 2 works with either ZODB4-wc2, or ZODB5, but not with ZODB4.
    # ERP5 does not currently work with ZODB5.
    # -> this leaves ZODB4-wc2 as the only choice.
    [ZODB]
    major = 4-wc2

    [erp5-defaults]
    wcfs-enable-default = true

Remove activate-WC2-preview.cfg as wendelin.core 2 is no longer draft
and there should be no need to use my personal repository and dirty
branch anymore.

Update metabase and fix a few minor problems, mostly:
 - use proper passwords for keystore and for postgresql
 - use Eclipse Temurin JRE, where the SSH tunnels work


See merge request !1077