Instead of installing the software inside slaprunner from 1.0 branch, use the
same branch as the tested one, this should allow to see regressions earlier
(before they got merged in 1.0)

this profile was modified in c6cc45ab (all: apply eclint to unify empty lines
at end of file, 2020-08-05) but does not use buildout.hash.cfg, so md5sum was
not automatically updated.

done with:

     npm install
     git ls-files | grep -v '\/unstable\/' | xargs ./node_modules/.bin/eclint fix
     git ls-files | grep buildout.hash.cfg | xargs ./update-hash

When full ERP5 / Wendelin software release compilation is done this requires more than 2GB of RAM due to groonga compilation constraints (cc1 gets OOM killed). Thus increase memory for DeploymentTests only.

Increase timeout to 15h as with new DeploymentTests we do compile from scratch and it might take a bit more than the previous default of 10 hours which reports false tests failure results.

Adjust the profile after we use switch-softwaretype instead of
softwaretype in slaprunner.

In test nodes we put the software_root folder out of the webrunner so we
can keep it for the following tests. Except that the shared folder has
been introduced by default recently, and it is still inside the webrunner.

Thus, between 2 tests the webrunner is deleted, so the shared parts are too,
but not the SR folder (which is marked as completed). Then in the successive tests
the software release fails to build, or the insances fail to isntanciate.

  Remove duplicated version definition at software level to prevent excessive duplication
  of the value.

/reviewed-on nexedi/slapos!590

bedba966

share parts with instance-runner.cfg

/cc @rafael @Nicolas @alain.takoudjou 

/reviewed-on nexedi/slapos!527

Those values are free to be used by tests in order to obtain working
IPv4 and IPv6 addresses or other parameters fetched during test node
instantiation.

Note that old-style keys (like LOCAL_IPV4 and LOCAL_IPV6) are kept for
backward compatibility.

/reviewed-on nexedi/slapos!471

seleniumrunner software recently became a full selenium server, which is
different from the original software, that was only intended as being a
minimal software to make firefox available for erp5testnode.

This caused several problems in erp5testnode, because erp5testnode needs
to be always able to build seleniumrunner from master branch (which is
probably wrong in the first place). With this software having lots of
components, the risk of build problems increased.

Also, it's something else, so let's make it another software.

Problem has been found, and as this mode emits a lot of data with test result
disable it.

It will allow to track behaviour of the test on various test nodes.

Software just to in install a test runner

This is required starting erp5.utils 0.4.51

Also add a missing md5sum for instance.cfg.in

/reviewed-on nexedi/slapos!362

Follow changes in erp5.util that will allow for stable test lines.

reviewed on nexedi/slapos!310

/reviewed-on nexedi/slapos!350

As sources URL depends on the branch, update it to correct one.