To run the benchmark locally:

 - Install software/slapos-sr-testing and create an instance
 - Source the shell script published by the instance to setup
   environment variables
 - execute `python_for_test -m unittest -v  test.benchmarks`

This promise was generally used to check the connection quality to the
backend with ICMP, by using ping. This is currently obsoleted by health-check
and other parameters in that group.

The parameter to setup the promise is provided by shared instance requester,
that person has no access to those results, as shared instances can't be
monitored directly, all results are only available to the cluster operator in
contrast to health-check, which results are logged to backend_log, to which
shared instance requester has access.

See merge request nexedi/slapos!1353

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.

See merge request nexedi/slapos!1348

See merge request nexedi/slapos!1345

software-dev.cfg will use most recent version of OSIE coupler code.

prevent auto-detection from linking against system libraries when they
are available.

See merge request nexedi/slapos!1341

Running theia with yarn start cause PATHs like this to be
added to $PATH

/srv/slapgrid/slappart15/tmp/yarn--1675226243379-0.20314216826775944/node

Similar to debian's default /etc/skel

this can be used to install linters such as pylint when the python
extension prompts for it

also add ~/.local/bin in user $PATH to prevent warning and to be
able to use pip installed packages from the shell.