Going from 0.0.0.dev4 to -> 0.0.0.dev8 zodbtools:

- Stabilized `zodb dump` format and layed ground for `zodb restore`;
- Taught `zodb analyze` to work with any ZODB storage (instead of being
  FileStorage-only tool) and to analyze a particular range of history
  (instead of crunching data for days on a large database);
- Added `zodb commit` tool that is handy in testing;
- Added ability to specify tid ranges in human-readable format, as in
  e.g. `zodb analyze data.fs 2018-01-01T10:30:00Z..yesterday`.
- Progressed on Python3 support.

See https://pypi.org/project/zodbtools/#zodbtools-change-history
for details.

Close to non-functional change, but removes PendingDeprecationWarning
about cgi.parse_qsl

0.0.0.dev4 to 0.0.7.post1 goes a long way. See
https://pypi.org/project/pygolang/#pygolang-change-history for details.

Recent pygolang is needed for wendelin.core 2.
Zodbtools also uses it starting from v0.0.0.dev5.

We already patch ZEO4 with TCP_NODELAY patch (see 5cf4cf1f "ERP5:
enable TCP_NODELAY for ZEO") and we will need to backport more patches
to ZEO4 branch for wendelin.core 2 to work correctly.

It's not only software/neoppod which uses ZEO, and it is not convenient for
all other software-releases to inherit from neoppod to use correct
version and build of ZEO egg. For this reason factor out details of ZEO
egg building into component/ZEO and let users use ${ZEO:egg} where ZEO
is needed. This way ZEO will be correctly installed for all users.

This patch should be a non-functional change. We switch to
nexedi/ZEO@5114f909 revision which corresponds to ZEO 4.3.1 +
TCP_NODELAY.patch

Adding other patches to ZEO4 needed by wendelin.core 2 will be done as a
separate step.

See merge request nexedi/slapos!836

stop-on-error during instantiation can lead to endless instantiation in some
cases, which disallows to create services required for given part to pass, and
in the same time in many cases the called scripts are smart enough to continue
and restart on error.

Thanks to this, it's much easier to find relevant configuration, and also logs
are becoming much more informative.

Avoid creating needless entries and minimise needless newlines, and reflect
this in test data, as in such case no backend_log is created, as nothing is
configured on backend Haproxy level.

SSL cache is unusable in context of caddy, same for the so called HTTPD home.
Those are old Apache leftovers.

It's a dict, and in SlapOS usage of Jinja2 it's good to see the type of
a variable immediately.

"parameter_dict" says nothing, whereas "software_parameter_dict" explains
source and purpose of the information.

There is needless duplication of information.

That's true, that those are templates, but the important information which
shall be in the name of the parameter is its purpose - a profile.

Section template-apache-frontend was not updated in buildout.hash.cfg

development.cfg is never used, and having split software definition in
software.cfg and common.cfg just makes development harder.

See merge request nexedi/slapos!832

This reverts commit 1c2d1c0a.
because NEO is not ready for such change.

nbd-host and nbd-port is not required in case of simplified configuration, use
boot-image-url-select instead.

5.2.2 brings in important fix that is needed for wendelin.core 2:
https://github.com/zopefoundation/ZEO/pull/160

They say that `zodbpickle.binary` is now much more lightweight on CPython2:
https://github.com/zopefoundation/zodbpickle/blob/master/CHANGES.rst#200-2019-11-13

software/caddy-frontend implements all requirements and apache-frontend is
not tested neither developed except small fixes, so it's ok to keep it for
reference or some small work outside of official tree, as other developers
might have urge to use it.