haufe.requestmonitoring already supports WSGI and Python3 and seems
used and maintainted.

For ZEO4, this was implemented as a monkey patch in ERP5, but this is
now supported in ZEO5, but not enabled by default.

The setting is only avaiable through ZEO's own ZConfig, but not with
ZODB's <zeoclient> so we also adjust the config to import ZEO and use
ZEO's <clientstorage>.

SIGUSR2 for reopening log files was handled by ZServer and waitress does not
handle signals at all, so we could handle this signal but Zope official
documentation recommends using logrotate `copytruncate`:
  https://zope.readthedocs.io/en/4.7/zopebook/MaintainingZope.html#log-rotation
  https://github.com/zopefoundation/Zope/issues/809

Let's pick up all fixes and improvements accumulated upstream to be used together with Zope4/Python2.

/reviewed-by @jerome, @levin.zimmermann
/reviewed-on nexedi/slapos!1332

See merge request nexedi/slapos!1331

fonts ipaex-fonts wouldn't download on version 1.0.210, and aren't
available in shacache for some reason.

ZEO 5.4.0 fixes several concurrency bugs and provides other
improvements. See changelog in https://pypi.org/project/ZEO/5.4.0/
for details.

Going from ZODB 5.6.0 to 5.8.0:

- removes leftovers of pre-MVCC read conflicts,
- relaxes assertion in tests that relate to NEO,
- brings up interface requirements in line with Wendelin.core 2 and WCFS,
- optimizes IO in fsrefs,
- fixes fsdump to match fsstats,
- provides new tests that exercise potential concurrency issues in
  storage implementations more thoroughly,
- provides other fixes and improvements.

Please see https://github.com/zopefoundation/ZODB/compare/5.6.0...5.8.0 and
https://pypi.org/project/ZODB/5.8.0/ for details.

Database password is now randomly generated.
Now test that the pre-filled password matches the mariadb url.

By inspecting current configuration stored in .data-disk-amount of the
partition configuration directory extend the conflict protection to really
observed configurations.

Adapt the README to follow real messages and explain a bit more the situation.

Patch 15e26abd explicitly declared
go version 1.17 for the 'helloworld' SR.

This was done at a time when we already had [golang1.17] in component/golang,
but the default was still go1.16. The explicit declaration allowed the 'helloworld' SR
to already switch to the newest go version.

Since patch d32524c3
we use go1.18 as our default version. In order to allow 'helloworld' to use our newest
SlapOS supported go version, it's therefore sufficient nowadays to simply remove the
explicit declaration.

/reviewed-on !1330
/reviewed-by @kirr

Database password in stack/lamp is now randomly generated.

See merge request nexedi/slapos!1329

Reuse stack and drop overcomplicated rsyslogd configuration.

A stack to share common configuration aspects.

See merge request !1328

  INFO (echo "# Do not edit -- this file documents how Postfix was built for your machine."; /bin/sh makedefs) >makedefs.tmp
  INFO ATTENTION:
  INFO ATTENTION: Unknown system type: Linux 6.1.6-arch1-3
  INFO ATTENTION:
  INFO make: *** [Makefile.in:33: Makefiles] Error 1
  INFO make: *** [Makefile:22: makefiles] Error 2

See merge request !1312

software/monitor: Clean-up 'default/base' monitor

forgot stack directory in 61ad458c

Add a webmanifest and a service worker to support "Add to home screen"


![image](/uploads/0ce9c6abdbe27291dd7fc8210d823c40/image.png)


Application name in this screenshot is "Theia SlapOS theia" because I requested with instance name "theia".

See merge request nexedi/slapos!1323