As a result installing erp5.util[testnode] and slapos.cookbook before
slapos.core will install a first slapos.core that will need to be
replaced and cause reinstallation each time. ( I guess )

this is not possible with ENVIRONMENT=

This reverts commit e542746a.

This function factorize the code to instanciate a recipe in a fake
buildout.
The new feature is that if running in a buildout directory, the recipe
will reuse the eggs from this buildout instead of trying to install eggs
again.

some tests use commands such as cat or sleep, so use slapos provided
version.

we now use slapos.cookbook:wrapper instead

slapos.cookbook:egg_test was not relying on anything that could not be
achieved by a simple slapos.cookbook:wrapper.
slapos.cookbook:wrapper are easier to manage because we don't need to
synchronize changes to profile and changes to egg.

At same time, start using new --python_interpreter parameter to pass our
generated interpreter with eggs

this is needed because the test needs to execute `python setup.py
test` within a directory containing the tested egg.

The instance working copy is a git clone from the software working copy,
so it should be using the same revision.

to also install test dependencies

Instead of running python setup.py that will install again egg with
maybe different versions of dependencies, use buildout way of installing
eggs and dependencies.

Also fix erp5-util erp5.util typo, we'll have to update test suites
defining a reporsitory for this.

thx @jerome

Depending on host python version the string "Build successful" renders
differently, so do not be too smart for it and simplify it.

In all examples of custom.js the Jupyter variable is capitalized, but
here it was not. Because of unknown reason, without Jupyter upgrade,
it stopped to working. Switching from "jupyter" to "Jupyter" fixes the
problem.

A quick slapos profile for Grafana, InfluxDB and Telegraf.

/reviewed-on nexedi/slapos!286