"wendelin" key is used in many places in the playbook and slapos so it
is required to find infromation with this key.

Remove temporary directory after exection.

/reviewed-on !29

Instead of chosing arbitrary directory and removing, often not
accessible directories, use standard mktemp for temporary location.

/reviewed-on nexedi/slapos.package!28

Since "[playbook] Make Wendelin like ERP5" Wendelin became compatible
with ERP5 SR, so compilation detection script shall support it.

@rafael - that's last one of my pre-prepared work for playbooks. Here in order to hide "internal" variables of playbook (like `backend_url_path`) and reuse them between different playbooks.

/reviewed-on nexedi/slapos.package!27

Wrong tags were used.

There is no need to differentiate Wendelin from ERP5, as both can use
same cluster configuration, and only BT5 list is different.

The ERP5 software type changed to default, as create-erp5-site has been
implemented there.

Upgrading to tag 1.0.56 requires to update the software_type of ERP5 to default, as it happened with recent changes in slapos.git repository for ERP5.

Cc: @rafael - please feel free to push it to proper audience.

/reviewed-on nexedi/slapos.package!25

- compat level was missing
- keep debconf disabled
- skip shlibs

Plus some clean up.

  Changes are from slapos.git repository.

  Unfortunally exising keys from open build service uses 1028-bit keys and debian 9 seems not reconize is as
  security enough, so on debian 9, we allow insecure repositories to allow re6st-node package be installed.

  This change can be re-worked in order to make the repository valid again.

  Grandenet is only a re6stnet service of VIFIB

Since buildout 2 no longer supports using multiple versions of Python
in a single buildout, we're now forced to use slapos.rebootstrap.

By adding Host: HTTP/1.1 header and checking the response the test
asserts, that server is able to serve on any hostname, which is
configured to server's IP address.

Note: skipped, as SSL is not fully configured on the server.

By adding Host: HTTP/1.1 header and checking the response the test
asserts, that server is able to serve on any hostname, which is
configured to server's IP address.

Do not redirect during request, just assert that redirection is
correctly returned form the server.

Keep test name generic and set to reasonable build time: 3h

Those tests are used by deploy-test ERP5TestNode testsuite.

By using separated frontend/backend requests and firewall configuration
allow to access ERP5 on public IPv4 of host on https port 443 and http
port 80.