* improve test coverage of instance.
 * version up ssh (for no special reason)
 * other minor fixes

/reviewed-on nexedi/slapos!629

/reviewed-on nexedi/slapos!634

If slaprunner itself was installed on a slapos which had shared parts
enabled, these shared parts will also be used while installing softwares
inside the slaprunner.

Because ${buildout:shared-part-list} is a multi line property, it was
not possible to generate .cfg files (which needs special handling of
multi-line strings) directly from software buildout (where jinja
templates are not yet available), so we use a trick of generating a
plain text file in software and parsing it during instance.

Instead of having to copy and paste the "ssh command", having a
clickable link is more user friendly. This integrates seamlessly with
ChromeOS secure shell app (eventhough the app does not do anything with
fingerprint as per version 0.19)

Because this slapos often is executed when just running `slapos` at is
in the $PATH, we should also consider special cases where users want to
call this script with another $SLAPOS_CONFIGURATION.

When $SLAPOS_CONFIGURATION is already set, ~/bin/slapos will not change
it, it will only set it when not set.

Because slaprunner might be instanciated in a different directory than
the shell user $HOME (like in recursive SlapOS), it's necessary to set
HOME to the base directory. For "bare metal" SlapOS, this would not make
any difference.

so that terminal uses terminfo from the same curses library.

Also change download URL to use https:// (no reason to use http)
Also switch to git format patch

this is the firefox we are currently using on testnodes. It's useful to
be able to run test with exactly same version to debug issues.

/reviewed-on nexedi/slapos!646

Most important changes:

 * promise tests are dropped, as this is implemented by test case
 * slave is always instantiated, to pass promise checks
 * move out some methods from the class
 * change the way how supervisor is called
 * adapt requestDefaultInstance to request slaves

New test system requires a lot of work for testing some edge cases of
caddy-frontend instantiation, so skip some tests for now.

caddy-frontend cluster stabilises only in case if slaves are present, as
otherwise slapos node instance won't run w/o errors, so request slaves
early.

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 nexedi/slapos!642

It is proven to work on Debian 10.

/reviewed-on nexedi/slapos!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 nexedi/slapos!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.