Update component to be suitable for osie-coupler

1.0.0 was not python2 compatible, setuptools ignored this

See merge request !1257

This brings updates of many dependencies on python3, while mostly
keeping the same versions for python2.

This enables a new `erp5-py3` test in software/slapos-sr-testing, which
should pass already, but with NEO and WCFS being marked as expected
failure or skipped for now.

This also brings pylint support on python3, which we will be able to
reuse in software/slapos-testing.
Co-authored-by: Kazuhiko SHIOZAKI <kazuhiko@nexedi.com>
Co-authored-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com>
Co-authored-by: Bryton Lacquement <bryton.lacquement@nexedi.com>

This bring new versions of jupyter, numpy and other scientific python
software. This impacts software/jupyter, which will now run more recent
versions and prepares stack/erp5 for python3 support, while not
impacting the python2 version.

This reverts commit 6c399134.

This is not really specific to python2, it is specific to ERP5, now that
ERP5 uses python3, the naming became not really good

This reverts 1b291415 (component/ghostscript: Workaround for slaprunner
paths with double slashs, 2021-06-02) and 4e9a9cf1 (component/tesseract:
Workaround for slaprunner paths with double slashs, 2021-08-19). We no
longer support slappruner and these commits were causing issues on
python3

statsmodels and websocket-client were pinned to Python3-only versions,
and slapos.toolbox was installed in develop mode from a Python3-only
revision.

fixup ac38a241 (Increase maximum ISO size to 20GB in KVMs., 2024-06-07)

With buildout3 all python2 software must extend this

Some Linux distributions, in particular server distributions such
as RHEL or SLE, have ISOs that are above 10GB in size.
This commits updates the maximum ISO size from 10GB to 20GB, so that
these ISOs can be used when requesting a new KVM.

See merge request nexedi/slapos!1550

In 55449aca (software/erp5: describe the allowed formats for family
and frontend names, 2024-01-01) we changed to a stricter definition of
zope and frontends partitions names, but because these objects allowed
additional properties, a partition not matching the pattern would be
anyway be accepted.

ptyprocess=0.6.0 uses flit as build backend

  The script were failing to generating the proof but it was continuing anyway.
  the set -e forces the script exit.

  This diff don't cause error since bash isn't run with -e but makes write_backup_proof useless basically.

pkgutil-resolve-name=1.3.10 requires flit_core as build backend.

This is used by component/slapos.

Use older numpy=1.22.0 to remain compatible with statsmodel=0.11.1.
Use older setuptools=44.1.1 to be able to install numpy=1.22.0.

dnspython=2.1.0 requires poetry as build backend.

Older Theia versions no longer compile inside test nodes since we
prevent using the system python.

Remove obsolete upgrade tests since we now upgrade from a Theia
version after merge request !1399.

Export (theia0) and export (theia1, ...) instances published
connection parameters twice, once without and once with the
resiliency connection parameters. Keep only that last one.

Use official SOAPpy=0.12.22 compatible with pip.
Downgrade zope.authentication=4.5.0 because 5.0 requires Python>=3.7.

Reverts 15871bbf

When using slapos.reboostrap to re-launch buildout with the version
of Python that was just installed, zc.buildout and its dependencies
are reinstalled for the new Python with the same egg versions. Thus
SRs which install Python 2 need to use Python-2-compatible versions
of setuptools, pip and wheel all along.

For this stack/slapos-py2.cfg is introduced.

It is also used to move all

```
[openssl]
<= openssl-1.1
```

from individual Python2 SRs to a common place.

Except for python2: keep beautifulsoup4=4.8.2.

beautifulsoup4=4.12.2 requires flit as build backend.

backcall=0.2.0 requires flit-core as build backend

entrypoints=0.3 rquires flit as build backend

pkgconfig=1.5.1 requires poetry as build backend.