repository was moved to nexedi

This macro generates an intepreters knowing its own sys.executable, so
it can be used as interpreter for theia's python extension to provide
code navigation, completion etc.

Until now it wasn't but with python3, import on future (not part of Python
library) means ${buildout:executable} is not enough. Anyhow, genbt5list should
be executed with all eggs IMO to avoid such problem.

I don't see any reason why we don't use upstream zope *versions.cfg files. This
just duplicates work and makes maintenance tedious especially now that we have
zope2, zope4py2 and zope4py3.

Also:
  * Remove pinned versions on eggs with newer version or already defined in
    Zope versions.cfg files.
  * Make sure that pinned versions in stack/slapos.cfg do not override Zope versions
    (for example ZConfig versions set in stack/slapos.cfg was creating a version
    conflict while installing another egg).

This fixes failures in erp5_dms:testWebDavSupport.

  Traceback (innermost last):
    [...]
    Module Products.ERP5Type.patches.OFSImage, line 94, in PUT
      return PUT_orig(self, REQUEST, RESPONSE)
    Module OFS.Image, line 665, in PUT
      data = data.encode('UTF-8')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 10: ordinal not in range(128)

Upgrading PyStemmer requires Cython.

build on zope4

wip : patches

update patches

reactivatee some patches & egg and remove dep to old ZSQLMEthod

fix zope patch

add Sessions product

reintroduce reStructuredText

use ExternalEditor compatible with Zope4

reinstroduce the config of _Z2PORT and _Z2HOST for testing

fix patch ?

add CMFDefault

Revert "add CMFDefault"

This reverts commit 3e3545ebd02fa188f4265301bbbf6b6b0f0dad9b.

pin eggs version

jerome: stop allowing version picking and pin versions

Since ERP5 commit 8f3b77517e (Force use of the new TimerServer, 2019-09-13)
the timerserver egg is not longer used, so it's not needed to install
and configure it.

* Note from @jerome: We have a useless dependency to
 https://pypi.org/project/alabaster/, a sphynx theme,
 but with oic v0.15.1 it's listed as a dependency
 ( https://github.com/OpenIDC/pyoidc/blob/v0.15.1/setup.py#L89 )
 so we don't have a choice. It was fixed later
 ( https://github.com/OpenIDC/pyoidc/issues/598 )
 but after python2 support was dropped.

With multiple security fixes

These comments are not updated automatically and very hard to update manually,
so it's better not to have them.

tempstorage 2.12.2 is from 2012 and misses loadBefore fixes which are
important when ERP5 is run with ZODB5 or ZODB4-wc2:

https://github.com/zopefoundation/tempstorage/commit/d187a86d
https://github.com/zopefoundation/tempstorage/pull/16

When the first loadBefore fix is not there, the problem manifests itself as
Zope not starting correctly with the following error in its log:

    2021-07-02 08:37:25,579 ERROR Zope.ZODBMountPoint Failed to mount database. <class 'ZODB.POSException.ReadConflictError'> (^@^@^@^@^@^@^@^@)
    Traceback (most recent call last):
     File ".../eggs/Zope2-2.13.30-py2.7.egg/Products/ZODBMountPoint/MountedObject.py", line 248, in _getOrOpenObject
       root = conn.root()
     File ".../parts/ZODB4-wc2/src/ZODB/Connection.py", line 405, in root
       return RootConvenience(self.get(z64))
     File ".../parts/ZODB4-wc2/src/ZODB/Connection.py", line 276, in get
       p, serial = self._load(oid)
     File ".../parts/ZODB4-wc2/src/ZODB/Connection.py", line 246, in _load
       return self._loadFrom(oid, self._storage)
     File ".../parts/ZODB4-wc2/src/ZODB/Connection.py", line 255, in _loadFrom
       raise ReadConflictError(oid)
    ReadConflictError: ^@^@^@^@^@^@^@^@

When the second loadBefore fix is not there, the problem manifests
itself as data corruption and sporadic POSKeyErrors
(https://github.com/zopefoundation/tempstorage/issues/8).

-> Fix both problem by using recent tempstorage with ZODB5 and ZODB4:

- ZODB5: just use tempstorage 5.2 egg
- ZODB4-wc2: use tempstorage 3 + loadBefore backports:
  https://lab.nexedi.com/nexedi/tempstorage/commits/3-nxd
- ZODB4: stays at 2.12.2 for now for this change to be as risk-free as
  possible. However, due to the fixes and e.g. https://github.com/zopefoundation/tempstorage/issues/8#issuecomment-873894941
  it makes sense to switch ZODB4 to tempstorage 3-nxd as well.

/cc @tomo, @romain, @rafael

This reverts commit 3e3545ebd02fa188f4265301bbbf6b6b0f0dad9b.