- rubygemsrecipe deployment mode now depends on `allow-picked-versions` by default

See theia's [changelog](https://github.com/eclipse-theia/theia/blob/v1.16.0/CHANGELOG.md#v1160---7292021), we update from 1.13.0 to 1.16.0.

Changes specific to slapos port:
 * We set `warnOnPotentiallyInsecureHostPattern` because the new warning is very intrusive ... but it might actually be very insecure. For now we don't have solution. We are tracking this in https://erp5js.nexedi.net/#/bug_module/20210819-20614EE
 * New libsecret component that is now required by theia
 * Switch to using vscode git instead of theia git, to use timeline ( see https://github.com/eclipse-theia/theia/pull/7997 )
 * globally version up slapos.core to https://pypi.org/project/slapos.core/1.6.18/

See merge request nexedi/slapos!1039

To have the timeline view

This is basically the same problem as in 1b291415
(component/ghostscript: Workaround for slaprunner paths with double
slashs, 2021-06-02)

The issue is now fixed in 1.16.0

Eventhough our current pattern is not the most secure, we have no other
choice for now that to use such insecure patterns.

In https://erp5js.nexedi.net/#/bug_module/20210819-20614EE we track possible
improvements to this situation.

This new version has a dependency to libsecret

Also adjust dependencies to the ones from https://github.com/eclipse-theia/theia/blob/v1.16.0/examples/browser/package.json
except api-samples which is not useful.

See merge request nexedi/slapos!1027

See merge request nexedi/slapos!931

The resiliency pull-backup-server status feed file `pbs-status-rss`
is generated by a cron running every 5 minutes. But there is a promise
that requires it to check the notifier status, meaning instanciation
fails until this file is available.

To allow the promise to succeed immediately, we generate the
feed a first time directly from buildout.

The resiliency notifier status feed file `notifier-status-rss`
is generated by a cron running every 5 minutes. But there is a
promise that requires it to check the notifier status, meaning
instanciation fails until this file is available.

To allow the promise to succeed immediately, we generate the
feed a first time directly from buildout.

See merge request !1041

we need to be explicit for extras.
Ping egg.

With multiple security fixes

See merge request nexedi/slapos!992

Follow-up for commit 98e7a29a (component/trafficserver: Version up to
9.0.2).

Drop patch from pull-request 7577, as it has since been merged upstream.

Zodburi 2.5.0 added support for demo: URI scheme:
https://github.com/Pylons/zodburi/blob/master/CHANGES.rst#250-2021-05-12

- due to a thinko in c170fe3e (ZODB: Provide ZODB4-wc2 which backports MVCC approach from ZODB5)
  4-wc2 revision was set on a ZEO(egg) section instead of ZEO(repository)
  section. As the result it was ZEO4 - not ZEO4-wc2 - that was installed.

  This was leading to hangs in tests with wcfs waiting for ZODB server to
  update it after a commit, but no notification was coming from ZEO at all.

  For the refrence: the reason ZEO4-wc2 exists at all is the backport patches
  that teach ZEO to send invalidations even on empty transactions
  (nexedi/ZEO@bf80d23d), and to include
  just-created objects into invalidations as well (nexedi/ZEO@f2fae122).
  Those changes are needed for WCFS to be always notificated on every
  transaction and with full set of changed objects.

- there was a typo: it was `revisions` instead of `revision`.

-> Fix both issues. Now it is ZEO4-wc2 that is installed for real when `ZODB.major = 4-wc2`.

The promise is commented out because it fails inside a test suite
due to port conflicts with the testnode of the test suite.

`srv/testnode/abc/inst/test0-0`  -> `t/abc/i/0`