To add a Database, user should request a slave instance. Each slave
instance is a database.

TODO: Destroy a slave instance should destroy related database

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:

nexedi/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 nexedi/slapos!1077

The setup "last,libc,none" allows lazy resolving of backend servers which is
crucial in order to being able to start when the domain does not exists (yet).

Follows dae1747d

This is needed for xlsx export

This solves the issue that ssh tunnels can not be used for database
connections, with sun's java they fail with an error containing:

    JCE cannot authenticate the provider BC

This is an alternate JRE from https://projects.eclipse.org/projects/adoptium.temurin

This version is the one used in metabase docker images

There was missing change in the default value to calculate default maximum
amount of parameters.

This fixes commit 2e6ccd02.

The default virtio-net-pci is not supported by some legacy OSes, so allow
customize it, to provide such support.

This is a dependency of slapos.cookbook[test] since 90650d2c (
recipe/test_postgres: test with a real postgres server, 2021-11-12) and
because we run software schema tests from slapos.cookbook in
software/slapos-sr-testing, we also need the dependency here.

tests with a real postgresql server, the mocked commands from 261a8e6b (test/recipe: update tests for postgres recipe regarding password update, 2021-11-11) were too unrealistic.

These tests with a real server revealed that the port option of the recipe was not used, this is fixed as well

See merge request nexedi/slapos!1083

even though the recipe has a required option for port, it was not used
and server was always listening on default (5432) port

exposing environment variable SLAPOS_TEST_POSTGRESQL_PREFIX containing
the location where postgresql is installed

taken from unstable lapp stack

Go1.17 is current stable Go release which, besides other improvements,
compared to Go1.16 generates code that runs 5-10-15% faster(*):

https://go.dev/blog/go1.17

It makes sense to use that version by default.

Cc'ing people who might be affected:

- caddy   (@luke)
- hugo    (@lu.xu)
- repman, restic  (@alain.takoudjou, @jerome)
- galene  (@tomo, @alain.takoudjou)
- gitlab  (@alain.takoudjou, @jerome, @lpgeneau)
- grafana (@jerome)
- theia   (@jerome, @xavier_thompson)

If for some reason Go1.17 default does not work for a software,
maintainer of that software release - please pin Go to Go1.16
explicitly inside that particular software-release.

(*) Go blog mentions 5% speedup on the average, but it was reported that
    sometimes for important inner loops the speedup can be as much as 15%.

/reviewed-by @jerome
/reviewed-on nexedi/slapos!1082

The history of deploy script can be seen in slapos.core package with:
git log -p master/bt5/slapos_web_deploy/PathTemplateItem/web_page_module/deploy_*

When server is running, use psql command to connect to server and issue
a query to update password.

This upgrade

- fixes Nxdtest to show proper traceback on error in configuration file

  nexedi/nxdtest@7b5add47

- adds preliminary support for PyLint[2]

  nexedi/nxdtest@72e36088

- and makes nxdtest to emit summary at the end of test run

  nexedi/nxdtest@9f413221

/reviewed-by @jerome
/reviewed-on nexedi/slapos!1081

Going Go1.16.8 -> Go1.16.10 brings in fixes to compiler, runtime and stdlib
including security fixes to linker, archive/zip package.

https://golang.org/doc/devel/release.html#go1.16.minor

Tested via:

- SlapOS.SoftwareReleases.IntegrationTest.Python2 (https://nexedijs.erp5.net/#/test_result_module/20211110-4DA2B2E), and
- SlapOS.SoftwareReleases.IntegrationTest.Python3 (https://nexedijs.erp5.net/#/test_result_module/20211110-40489859)

Going Go1.17.1 -> Go1.17.3 brings in fixes to compiler, runtime and stdlib
including security fixes to linker and archive/zip package.

https://golang.org/doc/devel/release.html#go1.17.minor

Tested via:

- SlapOS.SoftwareReleases.IntegrationTest.Python2 (https://nexedijs.erp5.net/#/test_result_module/20211110-4DA2B2E), and
- SlapOS.SoftwareReleases.IntegrationTest.Python3 (https://nexedijs.erp5.net/#/test_result_module/20211110-40489859)

In 805374b4 I established the way to run wendelin.core test.  There
component/wendelin.core/test-common.cfg preamble mimics what is setup
by software/neoppod/software-common.cfg in parts for NEO. However I
copied only neoppod into parts without neoppod-develop, and this results
in NEO being installed from PyPI instead of from git checkout.

Let's fix this because everything else - e.g. ERP5 and Wendelin software
releases - use NEO from git checkout which today diverged significantly
from what was last released to PyPI in April of 2019.

Thanks to @jerome for helping to find this out.

See merge request nexedi/slapos!1074