- add tun and netns for ims:

patchelf --set-rpath /opt/amarisoft/v2024-05-02/mme /opt/amarisoft/v2024-05-02/mme/lteims
setcap cap_sys_admin,cap_net_raw=+pe /opt/amarisoft/v2024-05-02/mme/lteims
ip tuntap add mode tun tun-ims
ip netns add ims
ip link set dev tun-ims name tun-ims netns ims
ip netns exec ims ip addr add 172.22.64.1/0 dev tun-ims
ip netns exec ims ip link set tun-ims up mtu 1400
ip netns exec ims ip route add default dev tun-ims

- SIM cards config needs to be modified:
  set correct impu and impi (001010000001312,
  001010000001312@ims.mnc001.mcc001.3gppnetwork.org)

- add /opt/amarisoft/setcap:

cat $1 | sha256sum -c <(echo 6bfcaf04b7da084874f34a77aacc1b2c6217c1d18bfda225f30dee950e32d48c -) --quiet &&
setcap cap_net_admin=+pe $1
chmod 644 /opt/amarisoft/setcap

box)

TODO, right now all this is needed:

- add ipv4 address on second tun
- run netcapdo with root
- launch IMS in root

SIM cards config needs to be modified:

- set correct impu and impi (001010000001312, 001010000001312@ims.mnc001.mcc001.3gppnetwork.org)

Grrr Jinja2 does not want me to write:

{%-   if any(node.get(x, 1) for x in ('admin', 'master', 'storage-count')) %}

See https://docs.python.org/3/using/cmdline.html#envvar-PYTHONHASHSEED

Setting a value will set the environment variable for all zope processes
and for the test runner.

Default behavior is:
  - for zope: do not set the variable, so default python behavior will
  be used ( equivalent to setting `0` on python2 and `random` on python3)
  - for test runner: generate a random value for each execution and
  print it, to make it easy to re-run a failing test with the same seed.

This means that ERP5 tests will likely reveal problems where code
depends on python2 behavior of deterministic hashing. To keep previous
behavior (and hide these problems), it's possible to set
python-hash-seed to 0 in test suite parameters.

See merge request !1553

See:
rubygemsrecipe!10
slapos.buildout!29

The CertificateAuthority tool in ERP5 uses UTF8 encoding for certificates,
but by default OpenSSL does not. This cause an error when using non-ascii
characters:

```
The localityName field is different between CA certificate and the request
```

To solve the problem, the Certificate Authority recipe should use the same
encoding as ERP5, which requires adding `-utf8` option when invoking
OpenSSL.

For instance, creating a certificate with `localityName` Москва
will give the following with the default OpenSSL encoding:
`\C3\90\C2\9C\C3\90\C2\BE\C3\91\C2\81\C3\90\C2\BA\C3\90\C2\B2\C3\90\C2\B0`.

UTF8-encoding this same string gives `\D0\9C\D0\BE\D1\81\D0\BA\D0\B2\D0\B0`,
which is what ERP5 expects.

See merge request !1552

This option will give fixed IP to each SIM card.

component/mavsdk: v↑ mavsdk (0.39.0 -> 1.4.13)
component/gwsocket: add gwsocket websocket server
software/js-drone: add frontend for subscriber
software/js-drone: use WebSocket for subscriber
slapos/software: run quickjs as a service

 * the default is already tested so drop TestRe6stVerificationUrlDefaultSlave
 * use locally provided URL to check re6st-verification-url, to not depend
   on external resources

!1501 did a good job with making default disabled, but during the code
review tests changes were not well checked.

logrotate test for the rapid-cdn SR have been failing for quite some
time because of a squid.log file created (and henceforth rotated) on
any slave instance of the CDN:

```
Traceback (most recent call last):
    self.assertEqual(
AssertionError: Items in the second set but not the first:
'squid.log_10.0.160.212.20240306.23h57m09s-20240307.00h00m02s.old.xz'
```

Since we do not want to test this file in that specific test, this
commit instead loosely check the content of the rotated files
directory.
In other words, the test now checks for the presence of the two
files to be tested, but avoid failing if other files exist.

This goes in line with the two following lines of that same test,
loosely checking for file absence instead of an empty directory.

/cc @tomo @luke
/approved-by @luke
/reviewed-on !1541