* master: (45 commits)
  stack/slapos: restore an old pin of importlib-metadata for py2
  component/apache-php: remove code pushed by mistake
  component/perl: version up 5.38.0
  component/fluent-bit: version up 2.1.10
  component/flex: version up 2.6.4
  component/apache-php: add missing xz in PATH
  component/ca-certificate: simplify pre-make-hook
  software/rapid-cdn: correct small typos in README.rst
  software/ors-amarisoft: Update changelog.rst
  software/ors-amarisoft: update RRH firmware to V1004.006
  software/ors-amarisoft: add reset function for RRH
  stack/slapos: version up nbconvert and dependencies
  software/slapos-sr-testing: correctly disallow usage of system python3
  software/erp5/upgrade_test: update old software url with backported fixes
  component/ca-certificates: don't use implicit `python`
  component/opencv: explicitly use slapos python
  component/open62541: add slapos python3 in PATH
  component/gtk-3: add slapos python3 in PATH
  component/gdk-pixbuf: add slapos python3 in PATH
  component/inkscape: add slapos python3 in PATH
  ...

1c4a3c69 (stack/slapos.cfg: version up eggs (requests 2.31.0 and
friends), 2023-10-04) broke component/nxdtest/test-py2.cfg and
others using pytest on python2

This part of 30804165 (component/apache-php: add missing xz in PATH,
2023-10-17) was pushed accidentally

This is required for xz archives

See merge request nexedi/slapos!1450

This is required because it depends on an older version of Jinja and
updating in 565f4986 (stack/slapos: version up Flask and friends
(itsdangerous, Jinja2, MarkupSafe, Werkzeug), 2023-10-12) broke jupyter
software

At the same time, move some pins from stack/erp5 to stack/slapos as they
become used by more softwares

previous patch - 24f5a96c (software/slapos-sr-testing: disallow usage
of system python3, 2023-10-02) - was incorrect, an `entry-point` is
required for a script to be generated.

We can not rely on system python here, it's a bit better to rely on
buildout's python ( the main reason is that it complies with
slapos-sr-testing not having system python ).

The implementation is a bit complicated, we can not just reference
${buildout:executable} in the profile, because doing so will cause an
infinite loop with rebootstrap and software installation never finish
because options of ca-certificates change at every run if they include
the python path. Instead, we use a pre-make-hook to rewrite the Makefile
without saving the interpreter in option. This python is only used
during the build process (to generate the certificate files) and not
used at run time, so it does not really depend on python strictly
speaking. Anyway, because it's a component used very early in the
bootstrap, we can not reference python here.

This software autodetects python2 and python3, so provide both

this component needs both python2 and python3