* master:
  software/headless-chromium: Update chromium to 114.0.5735.340

* origin/master:
  software/ors-amarisoft: enb: Adjust DHCP server to provide dedicated IPv6 to each Radio Unit
  software/ors-amarisoft: enb: Remove DNS options from for-RU DHCP configuration
  software/ors-amarisoft: Split dnsmasq.cfg into for-core and for-enb
  software/ors-amarisoft: Provide dedicated TAP interface for each Radio Unit
  software/ors-amarisoft: gnb: Move DRB configuration to standalone file
  software/ors-amarisoft: enb: Don't use #define inside DRB template
  software/ors-amarisoft: enb: Move DRB configuration to standalone file
  software/ors-amarisoft: Start to generalize existing lopcomm/multicell into multiRU slowly
  stack/slapos: version up erp5.util 1.0.75
  erp5testnode: update seleniumrunner to 1.0.345 to use firefox 115
  component/ca-certificates: Fix sbin location

We had to introduce a web page to bootstrap the web version of devtools
because since https://bugs.chromium.org/p/chromium/issues/detail?id=1232509
chrome debugger port no longer serve such a page via HTTP.

The URL also changed, /serve_file/@{version_hash}. pattern is no longer
used, both the devtools and the websocket endpoint are in /devtools

The test was made a bit more complete by actually making requests and
trying to connect to websocket endpoints.

Some problems were found with incognito and block-new-web-contents
options:
 - they are boolean type, but the software parameter serialisation is
 XML, which as of today does not support boolean types. This is left
 TODO for now
 - When both --incognito and --block-new-web-contents are true, the
 command line flag was --incognito--block-new-web-contents, which is
 unknown and was ignored. Some minmal changes are included to fix this.

By reusing recently added "split TAP" infrastructure we can adjust dnsmasq
configuration to provide unique IPv6 to each RU.

- ru_mac_addr becomes per-RU setting and without default. We talked with Lu, and
  since now all Lopcomm units are shipped from the factory with unique MAC, it
  both does not make sense to provide the default, and we can rely on all units
  to have different MACs and configure DHCP replies based on that.

- No need to provide /64 network to every RU. We cannot actually do that anyway
  because normally SlapOS provides /71 address range for its slaptap. In the
  new configuration everything works with smaller networks just ok.

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