runTestSuite.in uses __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.

instance.cfg md5sum has been omitted.

__hash_filename__ key is used to avoid clash with recipe.

hexagonit.recipe.download is replaced with slapos.recipe.build:download in
order to have the same approach everywhere and so __hash_filename__ key is
used to avoid collision with section:filename.

Use __hash_filename__ to avoid filename clash with recipes.

__hash_filename__ is used to avoid conflict of section:filename key with
hexagonit.recipe.download

A lot recipes treats filename key as something special, so for them support
additional key __hash_filename__, in order to avoid such clash.

Nextcloud's redis is causing `AF_UNIX path too long` on test nodes.

The first commit to adapt this test to slapos.testing was incomplete.
Now that nextcloud is fixed, we saw a few mistakes and python3
incompatibilities that are fixed in this commit.

This reverts commit 4636f49f.

This reverts commit 97884c30.

Package like lm-sensors, which depends on the kernel, shall be provided
by the OS.

/reviewed-on !642

It is proven to work on Debian 10.

/reviewed-on !640

slapos node collect require lmsensors, so use those ones provied with slapos
component.

/reviewed-on !641

Otherwise it will be installed without our special part, using system
curl.

/reviewed-on !639

/reviewed-on nexedi/slapos!635

also drop test_nextcloud_promises as promises are now checked by
framework.

/reviewed-on nexedi/slapos!636

Prove that:

 * VNC is accessible
 * monitor-base-url on each partition is accessible with password extracted
   from the main partition

frontend-instance-guid and frontend-additional-instance-guid are used to
control where the websocket frontend shall end up.

Real frontend is always requested.

Additional frontend is requested only if frontend-additional-instance-guid is
not empty. This frontend is published as url-additional and can be used for
access to users from some restricted networks.

publish-early does not work in this case, and monitor password is stored
in buildout elsewhere anyway.