The section template-slapuser-script creates the "bin/slapos" wrapper
which is needed inside runner-import.sh script.

The fixes a conflict with 'runner-exporter' due bugs in cns.recipe.symlink

Anyway, a much better idea would be to add ~/software_release/bin to PATH.

These keys are not managed by trust of a certificate authority, just by
"trust of first use" so it does not make sense to use a key authority.

This also cause difficulties to publish the key fingerprint as a
parameter, because we can't get the key fingerprint until the authority
service is started.

Also enable ecdsa key.

This fixes random failures with slaprunner tests, because the published
fingerprint was never correct on first buildout run.

Existing webrunners will have a new ssh host key after this.

This reverts commit dcd2f8d6.

It has to be redone with proper test coverage.

Since the introduction of shared parts, there is no guarantee about
the location of sqlite3 binary.

/reviewed-on nexedi/slapos!465

This should fix resiliency tests

/reviewed-on nexedi/slapos!439

The path of software release in webrunner is like: `/srv/slapgrid/slappartXX/srv//runner/project/slapos/software/soft/software.cfg`  because ~/srv directory in webrunner is set with a / at the end:

Changing that path will modify the URL of software release in webrunner, this is why we should always keep it as: `/srv/slapgrid/slappartXX/srv//`

/reviewed-on nexedi/slapos!175

Further rewrite should be done but at least there's no awk code anymore.

/reviewed-on nexedi/slapos!172

  If there is no error, the raise can be missleading.

Use the same exclude patterns (receiving end may want to exclude a file set
different from the time backup was exported, or may have a different set of
buildout-managed files which would be dangerous and misleading to
overwrite).

Otherwise, slaprunner-supervisord crashes because of unknown paths

This message is also available via a promise

If slapgrid fails, print the end of instance/software log in resilient log.
Now an the exit-code-file is always written, even if runner-importer fails.
The promise on this file gives the URL where the resilient log can
be accessed, to simplify the debugging

It includes more debugging lines, not deploying a slapproxy (no need anymore thanks
the free-port selection recipe), and not delegating some work to a cron job.

slaprunner: uses sshkeys_authority recipe to manage openssh keys, otherwise they may change at any slapos run

This makes easier the development of the webrunner, as it can be deployed within a webrunner

Changes include:
  * new parameter "no-ipv4-frontend" to prevent the request of an ipv4 frontend. The webrunner cannot provide one, so let's get rid of failing promises.
  * new paramaters to define the ports of the ssh servers (for runner-importer and runner-exporter). Then no colliding when servers run on the same IP.