There have been push force on master branch, and 1.0.309 seems to be the
result of merging an old version of master branch, the commits between
1.0.308 and 1.0.309 are same as commit on master branch but with
different hashes and when we try to merge master in 1.0 there are
conflicts.

This commit resets to the same state as 1.0.308, it was done with:

  git resore --source 1.0.308 :/
  git commit -a

so it revert all these commits so that we can merge master again.

See merge request !1372

The instance-gitlab-test.cfg.in was removed.
We should test the cfg which used in production,
not a dedicated cfg for testing

See merge request !1368

Add missing libxcb to rpath

This reverts commit ca5ba490.

It's actually a good idea to update our pandas version (0.19.x is
already 7 years old, in one project we recently run into a bug of this
pandas version).

We only need to prepare erp5 with few changes so that it also support
those newer versions. This preperation was done in nexedi/erp5!1738.

/reviewed-on nexedi/slapos!1355

using ERP5: erp5!1545

See merge request !1122

1) stack/erp5/zope-versions.cfg
2) stack/slapos.cfg
3) component/ZODB/buildout.cfg.

and remove stack/erp5/ztk-versions.cfg as we need only small part of it.

stack/slapos.cfg should be listed in the begining of software release extends list.

ERP5 now only supports WSGI

This needs a recent enough erp5, with the following commit:
zopewsgi: configure threads count and large_file_threshold with argparse

We only support wsgi now.

TODO: revert slapos.package@63da524b

Only wsgi is supported with Zope 4

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

This was using `python` which is not always available

Also re-export package-lock.json for the format from npm we currently
have in theia

See merge request nexedi/slapos!1369

See merge request nexedi/slapos!1322

Compile xdpyinfo for use, in case of debug.

bash tests files (*..bash) was not included to nxdtest.

See merge request nexedi/slapos!1365

Shorten the socket path
Add a promise to check socket

This updates python extension to a version supporting only python3.

To have full python2 support, it's possible to download
https://open-vsx.org/extension/ms-python/python/2020.10.332292344
and use "Install from VSIX" option and manually apply the patch to fix
perfomance issue with buildout paths:

    curl https://lab.nexedi.com/nexedi/slapos/raw/bdb7777beb34d8840cbbc498adba7a55d521079b/component/theia/ms-python-disable-jedi-buildout.patch | patch  ~/tmp/vscode-unpacked/ms-python.python-2020.10.332292344.vsix/extension/pythonFiles/lib/python/jedi/inference/sys_path.py