Use slapos.recipe.template instead of slapos.recipe.template if possible

Harmonize template keys :
rendered -> output
template -> url
template = inline: -> inline =

Delete "mode" key

See merge request nexedi/slapos!1151

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

This teaches nxdtest to detect leaked processes and to clean them up
automatically instead of letting tests stuck because of them. See
nexedi/nxdtest@0ad45a9c and
nexedi/nxdtest!9 for details.

New dependencies of nxdtest are:

- psutil (already covered by stack/slapos.cfg),
- pytest-timeout, and
- setproctitle

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

These comments are not updated automatically and very hard to update manually,
so it's better not to have them.

The previous way to initialize ~/srv/mariadb relied on /bin/mv, so that
it's atomic, making [template-mysqld-wrapper] idempotent (think of a
crash in the middle mysql_install_db). However, mv only works if
~/srv/mariadb is a simple directory: it fails if it's a symlink,
a mount point, or a subvolume (btrfs).

When using extra storage devices for some data, one may prefer to only
put the data (e.g. ~/srv/mariadb) and not the whole slapos partition.
Then if we want a resilient ERP5 with catalog's datadir on a separate
storage device, the importer script must be able to reinitialize
~/srv/mariadb whatever its type.

Install setuptools_scm before python-dateutil (which has it in setup_requires) so that the version can be controlled by buildout

See nexedi/slapos@f1e7230e

Factor-out things that provide components for ZODB stack from software/neoppod/
into component/ZODB/.

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.

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

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

For some SR, it implies the following upgrades:
- decorator: 4.3.0
- gitdb2: 2.0.5
- smmap2: 2.0.5
- subprocess32: 3.5.3

Since 10.4, it seems mysql_install_db does not take anymore
BASEDIR/lib/plugin as default value for plugin_dir.

runTestSuite.in uses _update_hash_filename_ compatbility to avoid clash with
section's filename key.

As software.cfg is extended by other software releases rename the template
part to template-neo in order to avoid clash of sections.

This fixes previous commit.

We'll add monitoring to NEO so some parts are also moved there from ERP5.

mock is only a test dependency for zobduri

Recent setuptools found a way to install by downloading wheels from PyPI.
But we want to control the versions of all components.

BTrees 4.4.1 is from early 2017. BTrees 4.5.0 contains fix for crash
when deallocating items:

https://github.com/zopefoundation/BTrees/issues/75  
https://github.com/zopefoundation/BTrees/commit/16e70dd337

It is similar crash and fix to this one in wendelin.core:

nexedi/wendelin.core@d97641d2

and in Python 2.7.15:

nexedi/slapos@8e098385 (comment 72575)

BTrees 4.5.1 is a small maintenance release over 4.5.0 and is currently
latest BTree release.

/cc @jm, @vpelletier, @kazuhiko, @jerome
/reviewed-on nexedi/slapos!550

For the test suite, all plugins are still loaded if no engine is specified.

Loading TokuDB whereas RocksDB is used is quite annoying because:
- TokuDB creates many threads
- RocksDB opens many files
We had systems where lsof takes a few minutes to output 10 million lines.

This will also make the datadir a bit cleaner.

They are dependencies of slapos.toolbox and we already agreed to put slapos.toolbox version in a shared file.

/cc @jerome @jm

/reviewed-on nexedi/slapos!502

See sqlite-mixin.cfg to skip the building of MariaDB.

/reviewed-on !427