* master:
  software/ors-amarisoft: fix check-baseband-latency

* origin/master:
  component/firefox: set $GSETTINGS_SCHEMA_DIR in the wrapper

This fixes a crash happening after `setFile` selenium command under
some conditions (it does not always happen, but I did not investigate
in which conditions it happens exactly).

[Parent 94283, Main Thread] ###!!! ASSERTION: No GSettings schemas are installed on the system: 'glib assertion', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:164

* origin/master:
  component/firefox: use firefox 115 / geckodriver 0.33.0 by default
  software/seleniumserver/test: verify that authentication is required
  software/seleniumrunner: remove useless [versions] set in stack/slapos.cfg
  software/seleniumserver: remove useless bytes= for password recipes
  component/firefox: remove firefox 52 / geckodriver 0.16.1
  software/seleniumserver: add firefox 115 and remove firefox 52
  component/firefox: add firefox 115.3.1esr and geckodriver 0.33.0
  component/alsa: version up alsa-lib 1.2.10

See merge request !1470

* master:
  software/gitlab: update gitlab-ce to fix npm error
  NEO: add missing software.cfg.json
  software/ors-amarisoft: ru/lopcomm: Simplify and clarify cu_config.jinja2.xml
  software/ors-amarisoft: Fix pythonwitheggs to explicitly specify in-SlapOS lxml
  component/python-2.7, component/python3: fix readline termcap library detection.
  component/readline: remove outdated readline5.
  component/mariadb: build with libedit instead of outdated readline5.
  component/libedit: add.
  software/ors-amarisoft: Start to organize Radio Unit related bits under ru/

Since yesterday, software/gitlab can no longer be installed with an
error while installing gitlab_npm:

    ERR! Invalid dependency type requested: alias

This is because we are using npm install to install a repository which
uses yarn.lock to pin versions, so the install was done without having
the dependencies pinned. Using an old yarn for this repository does not
seem so easy, so we just have made a commit to convert the yarn.lock to
a package-lock.json, so that we don't have to update the tooling here.

Once we update, we'll rework this part of the software to use yarn, it
seems gitlab still uses yarn in more recent versions.

`git describe` also produced different (more correct) output, because
some tags were missing in our mirror of gitlab-ce.

this applies to software/seleniumrunner and testnodes

this was just not tested

the default bytes is just fine

We can use mathematical relation in between ports, channels and tx/rx endpoints
to bring structure and clarity in RU setup.

Also, while on it, document how tx/rx data flow are organized as it was not
clear just from reading ORAN specs and I had to deduce it.

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