Allows defining a domain name pointing at caucase's IP, and a custom port
pointing at whatever port caucase is being made available on to all
services and users. This makes it possible to change caucased's IP address
without having to reissue all certificates when certificate-validating
library given a caucased-issued certificate tries to access the CRL
distriution point.
software/caucase still pusblishes the plain IP & port allocated by slapos.

WIP: Host header is not sanitised by haproxy:
  curl -vk --header 'Host: 10.0.11.117:2150/unit_test_0/VirtualHostRoot/vh_unit_test_0/?' https://10.0.11.117:2150/unit_test_0/vincent/

Instead, use the requests' Host header.
This allows accessing the balancer under any name, including ones not
expected by the backend.

XXX: should actually factorise code.
XXX: test

This is more representative of how this is supposed to be used.

So that this external interface keeps working, allowing automated log
extraction to keep working.

Also upgrade slapos.toolbox to have better promises.

See merge request !1711

Previous version was not uploaded properly to shacache

Version up zc.buildout 3.0.1+slapos008
Version up zc.recipe.egg 2.0.8.dev0+slapos008

See merge request !1709

See merge request !1707

We need also to start gitaly service before start gitlab restoration.

They are already in slapos stack

- add power_on parameter
- fix amarisoft_version parameter in ue
- fix com address in UE configuration
- add nginx for the websocket

During tests a hostname and port is provided instead
of an URL, so hostname needs to be retrieved

Update gNB configuration to match 2024 Amarisoft

User is still allowed to input a hidden parameter
to change the version

After dropping _force_slapos_node_instance_all tests with parameter propagation
need special treatment:

 * during first waitForInstance it is needed to wait for instance for the
   parameterto be requested to the master
 * during second waitForInstance the parameter is being propagated to other
   instances

This is solved by waitForInstanceWithPropagation

In some cases tests are modyfing in-place partitions (eg. .slapos-resource)
in order to mock some states. Then it's required to force instatiation with
waitForInstanceWithForce.

In other places additional, sometimes conditional, processing is added in
order to account for non forced default processing.

Do not force --all for instance in order to test real instantiation.