After d8409763 (NEO: default ZODB was changed to 5) wendelin.core tests
started to fail to build because files, that the tests extend from, were
renamed on neoppod side. Example failure:

    An internal error occurred due to a bug in either zc.buildout or in a
    recipe being used:
    Traceback (most recent call last):
      File "/opt/slapos/eggs/zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 2359, in main
        user_defaults, command, args)
      File "/opt/slapos/eggs/zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 312, in __init__
        data['buildout'], override))
      File "/opt/slapos/eggs/zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 1974, in _open
        seen, processing))
      File "/opt/slapos/eggs/zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 1974, in _open
        seen, processing))
      File "/opt/slapos/eggs/zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 1974, in _open
        seen, processing))
      File "/opt/slapos/eggs/zc.buildout-2.7.1+slapos019-py3.7.egg/zc/buildout/buildout.py", line 1940, in _open
        with open(downloaded_filename) as fp:
    FileNotFoundError: [Errno 2] No such file or directory: '/srv/slapgrid/slappart49/srv/project/slapos/software/neoppod/software-zodb5.cfg'

-> Fix it by adjusting wendelin.core tests correspondingly.

Similarly to 339490eb (components/zodbtools: reorganize test profiles)
make each test profile to explicitly indicate which configuration it
tests against.

Drop support for testing pristine ZODB4 - now only ZODB5 and ZODB4-wc2 remain.

We can drop test coverage for ZODB4 because slapos mainline switched to
ZODB5 to be used by default in 1c51c4cd (stack/erp5: version up all zope
stack (Zope 4.8.7), and because wendelin.core 2 works only with ZODB5
and ZODB4-wc2, but not with plain ZODB4.

In Wendelin we mostly always want to run our zopes with the soft limit
set to the hard limit.

/reviewed-by @jerome, @jm, @rafael, @vpelletier
/reviewed-on nexedi/slapos!1465

---

This patch was already added in nexedi/slapos!1451, but
removed (by force push), due to issues discussed in nexedi/slapos!1451 (comment 193296).

nexedi/erp5@39369169 added the functionality to ERP5 to
set its soft limit of allowed open file descriptors to the system wide hard limit.
This parameter is useful for Wendelin based instances where the 1024
limit is easily reached.

With this patch, this parameter can also be set via SlapOS, which
simplifies usage of the Wendelin SR.

/reviewed-by @jerome, @jm, @rafael, @vpelletier
/reviewed-on nexedi/slapos!1465

---

This patch was already added in nexedi/slapos!1451, but
removed (by force push), due to issues discussed in nexedi/slapos!1451 (comment 193296).

Comments need to be at the start of the line.

The SLA unique_by_network was not requested at all when any SLA was set
in the resilience. Now we put unique_by_network for all instances
without SLA.

this is needed for slapos-node package compilation

This is a fixup of 5f6a2eb8.

util-linux needs gcc 8+ in order to avoid error:

libuuid/src/gen_uuid.c:536:33: error: initializer element is not constant

See merge request nexedi/slapos!1489

See merge request nexedi/slapos!1457

There are more recent versions, but they don't use pyproject.toml for
metadata.

Here we want a version with python3.11 support

This comes with a patch because the setup.py does not have version,
which is not supported with our old tooling.

This section is just for setup, it does not make sense to generate
scripts here and it cause errors when another section uses the same
technique.

Note that we don't use 3 yet because nexedi/pygolang@6446a0be

Webrunner was using this and it's natural for users coming from
slaprunner to find slapos wrapper in ~/bin/slapos, but where theia is
very incompatible is that ~/bin/sla[TAB] will another slapos-standalone
which will conflict with the one from theia.

Even if 'sed -i' is not posix and we should not use system sed this way:
- even busybox supports this option
- we already use it in so many other places that it does not make sense to
  to impose ourselves such extra dependency

If we plan to fix all 'sed -i', alternatives to [sed] are:
- patch
- 'perl -pi -e' (perl is already built for openssl)

And we should first have a mechanism to prevent misuse of system sed.

Going 0.139 -> 0.140 introduces the following changes:

    nexedi/slapos.toolbox@0.139...0.140

Test results: https://erp5js.nexedi.net/#/test_result_module/20231130-F8B9BE8D

erp5 and slapos-master failed but the failures seem to be unrelated and
it was already the same before on master:

https://erp5js.nexedi.net/#!display_with_history?p.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F22%26view%3Dview_result_history&p.editable=true&p.selection=8c63bd5c5d74765e1a10d5276fd66ae6914e949b&p.history=235a69ba30d222bbf3194ffbae652f43f6dabe87&p.selection_index=1&p.page=form&p.jio_key=test_result_module%2F20231130-5E15B7D0%2F22&n.jio_key=test_result_module%2F20231130-5E15B7D0%2F22&n.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F22%26view%3Dview_result_history

https://erp5js.nexedi.net/#!display_with_history?p.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F57%26view%3Dview_result_history&p.editable=true&p.selection=8c63bd5c5d74765e1a10d5276fd66ae6914e949b&p.history=235a69ba30d222bbf3194ffbae652f43f6dabe87&p.selection_index=41&p.page=form&p.jio_key=test_result_module%2F20231130-5E15B7D0%2F57&n.jio_key=test_result_module%2F20231130-5E15B7D0%2F57&n.view=https%3A%2F%2Ferp5js.nexedi.net%2Fhateoas%2FERP5Document_getHateoas%3Fmode%3Dtraverse%26relative_url%3Dtest_result_module%252F20231130-5E15B7D0%252F57%26view%3Dview_result_history

Now that testnodes are using ipv6 range, we can safely put back this
check in place.

Werkzeug 3.0.0 is not compatible with Python3.7:

  File "/opt/slapos/eggs/werkzeug-3.0.0-py3.7.egg/werkzeug/serving.py",
line 76, in <module>
    t.Union["ssl.SSLContext", t.Tuple[str, t.Optional[str]],
t.Literal["adhoc"]]
AttributeError: module 'typing' has no attribute 'Literal

Now that testnodes are using ipv6 range, we can safely put back this
check in place.

This reverts commit 51a16b0b.

See merge request !1484

- remove no longer used ru/lopcomm/supervision.jinja2.py
- restore removed `+ keep on touching RU watchdog` comment.
  Now it relates to ru/lopcomm/stats which became responsible for this function.
- move code of RU-netconf-connection promise to be located nearby stats service
  because this promise interacts with that service, and grouping code by
  interaction makes it easier to understand for humans. Previously
  RU-netconf-connection was interacting with supervision service whcsh is gone
  after the patch in question.
- use double vertical space to delimit logical sections from each other.

open questions:

- before the patch in question stats code was reconnecting after each error
  with 10 seconds pause. Now it logs it wants to reconnect but does _not_
  because top-level `while True` was removed. Was that intended?

  If it was not the intent then new stats code will fail after any single error
  and won't reconnect to RU by itself.

/reviewed-by @lu.xu
/reviewed-on !1483

Similarly to sdr-busy, if we have several radio units, we want each of them to
have its own rx-saturated promise.

See nexedi/slapos.toolbox!126 for
corresponding part in slapos.toolbox that makes check_rx_saturated per-RU
configurable.

Not touching gnb.jinja2.cfg as currently gnb does not support multicell at all,
and in the future it will be sole enb.cfg to handle both LTE and NR
simultaneously.

/cc @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu
/reviewed-on nexedi/slapos!1485

If we have several radio units, we want each of them to have its own sdr-busy promise.

See nexedi/slapos.toolbox!125 for
corresponding part in slapos.toolbox that makes check_sdr_busy per-RU
configurable.

Not touching gnb.jinja2.cfg as currently gnb does not support multicell at all,
and in the future it will be sole enb.cfg to handle both LTE and NR
simultaneously.

/cc @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu
/reviewed-on nexedi/slapos!1485