This was sometimes causing false positives, for example if site have
only one hit and this hit takes more than one second, apdex is 0% and
promise failed, it seems useful to at least have a way to disable.

We are discussed on nexedi/slapos!1716 (comment 225941)
an idea of introducing a "minimal number of hits" parameter to not
detect this false positive on sites that are not accessed enough to
calculate a meaningful apdex.

This follows the new notation of slapos master.

golang tests fail because of https://github.com/golang/go/issues/71077.
This patch backports https://github.com/golang/go/commit/d1d93129506c78cc8ee25644384286822d93c81a.
go1.22 and go1.23 include this fix already [1].

[1] https://go-review.googlesource.com/c/go/+/640315

/reported-by @romain
/reviewed-by @jerome @kirr @tomo
/reviewed-on !1713

This reduces maintenance work. go1.4 and go1.17 are used for
bootstrapping. go1.15 is used for gitlab.

/reviewed-by @jerome @kirr @tomo
/reviewed-on nexedi/slapos!1713

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