see nexedi/slapos!1215

MarkupSafe 1.0 is not compatible with Python 3.8

fixes CVE-2021-33503

fixes PVE-2022-47833

software/{gitlab,nextcloud}: update options to new redis recipe

theia, erp5testnode are both running a slapos standalone. We don't
change slaprunner to python3 because it's not maintained anymore and
should disappear in the near future.

Use the exact version number displayed on the pypi index, because our shacache system is based on the URL which contains a package version number.

This partially reverts ee733f9d because
of issues with python3

In slapos.core commit 425f5bb7b (slapgrid: replace platform.linux_distribution()
with distro.linux_distribution(), 2022-03-21), a dependency to distro
was introduced. Because tests run with slapos.core fetched from git, they
already started to fail because of the missing version pin.

The pin is made to the latest version for both python2 and python3.
Usually we take the latest version compatible with python2, but I just
thought this way was probably better.

Several places pin mock egg individually. There are pins to `mock = 3.0.5`
and pins to `mock = 2.0.0:whl`. Mock 3.0.5 is the last version that
supports Python2 and can be considered as "current" in our context today.

For nxdtest we are going to add pytest-mock, which depends on the mock,
which, if not consolidated, will need to add another `mock = 3.0.5`
somewhere.

-> Stop doing that and move mock pinning into stack/slapos.cfg.
This way it will be even easier for upcoming Python3 support, because in
stack/slapos.cfg we can add per-Python3 [versions] with pins adjusted as
needed for py3, but all still in one single place.

Leave `mock = 2.0.0:whl` pins intact to be updated when needed by
maintainers of corresponding software releases:

    software/slapos-sr-testing/software.cfg:mock = 2.0.0:whl
    software/slapos-testing/software.cfg:mock = 2.0.0:whl
    software/wendelin/software-kerastensorflow.cfg:mock = 2.0.0:whl