pygolang: Accompany python-interpreter with gpython-interpreter to run gpython instead of std python

With python-interpreter staying the default for pyprog, but possible to adjust.

We will need gpython-interpreter for ERP5 to use bstr+ustr as builting string types.

Remove [gpython] script in favour of gpython-interpreter since both provide the
same thing but via slightly different ways internally ([gpython] was generating
bin/gpython via setuptools and [gpython-interpreter] does it by hand with
user-visible result staying the same).

/cc @kazuhiko, @jerome

pyprog macro, added in 0ee52376 (Generalize how nxdtest python script is
generated into pyprog recipe macro) works by generating buildout code at
runtime in text form. This way it should be careful when substituting strings,
because if those strings contain \n, then intended control flow might become broken.

For example when using pyprog with eggs = ${eggs:eggs} from stack/erp5/ ,
buildout breaks because erp5 defines eggs as multiline list:

    INFO     self.buildout.parse("""
    INFO   File "/srv/slapgrid/slappart47/srv/runner/software/7f1663e8148f227ce3c6a38fc52796e2/eggs/zc.buildout-2.7.1+slapos020-py3.9.egg/zc/buildout/buildout.py", line 1352, in parse
    INFO     sections = zc.buildout.configparser.parse(
    INFO   File "/srv/slapgrid/slappart47/srv/runner/software/7f1663e8148f227ce3c6a38fc52796e2/eggs/zc.buildout-2.7.1+slapos020-py3.9.egg/zc/buildout/configparser.py", line 241, in parse
    INFO     raise e
    INFO zc.buildout.configparser.ParsingError: File contains parsing errors:
    INFO         [line 18]: 'python-barcode\n'
    INFO         [line 19]: 'SOAPpy-py3\n'
    INFO         [line 20]: 'suds-py3\n'
    INFO         [line 21]: 'neoppod[admin, ctl, master]\n'
    INFO         [line 22]: 'cython-zstd\n'
    INFO         [line 23]: 'msgpack\n'
    INFO         [line 24]: 'mysqlclient\n'
    INFO         [line 25]: 'PyMySQL\n'
    INFO         [line 26]: 'ZODB\n'
    INFO         [line 27]: 'zodbtools\n'
    INFO         [line 28]: 'psutil\n'
         ...

-> Fix it via indenting eggs list like we already do with pyinit code.

/cc @kazuhiko, @jerome

See merge request nexedi/slapos!1572

to avoid the following error:
relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC

software/osie-coupler: keep the build source directory instead of having another open62541-source part.

software/slapos-sr-testing: add erp5-py3

---

WIP ERP5: XXX dumps() parameter for longrequest promise 🚧

Not sure why it was OK on python2 and not sure if this has to be done
or the promise code needs to cast the results of getConfig()

---

py3: do not enable NEO test yet 🚧

at this point they all fail after long timeouts, because neo does not
support py3 yet

stack/erp5: version up APacheDEX 2.0 (py3 only)
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 reverts commit 6c399134.

This is a fixup of 210e2d76.

Without full diff it's often impossible to understand the problem of JSON
schema introduced by the developer.

Upgrading pygolang in the context of SlapOS brings in some minor speedup
and fixes, but is mostly needed for ors-amarisoft software release due
to fix for a memory leak and optimized timers:

nexedi/pygolang@2ec5e96b
nexedi/pygolang@044deb35

The full list of the changes is below:

nexedi/pygolang@pygolang-0.1...pygolang-0.1-69-g044deb35

/cc ORS team (@jhuge, @lu.xu, @tomo, @xavier_thompson, @Daetalus)
/reviewed-by @jerome
/reviewed-on nexedi/slapos!1569

Similarly to wendelin.core (see ad34ff4a "wendelin.core: Always use git
checkout for both release and development version") let's switch pygolang to
install via git checkout for both release and tests.

This way we avoid dependency on pypi and will be able to do minor updates
without doing bigger to-pypi releases. Always using git checkout also helps
security a bit because we remove reliance on trust to tarball received from pypi.

/cc @kazuhiko
/reviewed-by @jerome
/reviewed-on nexedi/slapos!1569

@jerome reports ue/cell/* schemas are not valid JSON and he is right: in
30179be5 I made a mistake to add extra trailing " after propertyOrder
integer value. Fix that.

See merge request nexedi/slapos!1564

  They are json-editor specific features and are not part of the json schema

  By using ref to ../ru/input-schema.json you append oneOf list and dont extend the
  current list.

  This fixes validation properly when oneOf the values are used.

  Done by Thomas Gambier