Just download it and use file:// schema, so it can be used with locally
available profile and fetched from the url.

Previously the instance was downloading content from the profile URL,
which is simply bad idea.

Thanks to referring it, the checksum can be managed by buildout.hash.cfg

See merge request nexedi/slapos!1013

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

sotware/caddy-frontend: Use instance-caddy-replicate.cfg to replace buildout-switch-softwaretype.cfg

Because when using the switch-software, the
buildout-switch-sofwtwaretype.cfg will not be generated, see
https://lab.nexedi.com/nexedi/slapos/blob/master/slapos/recipe/softwaretype.py#L264-267
So use instance-caddy-replicate.cfg instead, which has same effect.

Changes explanation:
slave_reference.lower(): The configparser which the current buildout
using is case sensitive, which cause some options cannot be found.
slap_software_type: The recipe softwaretype need this option, but
switch-softwaretype doesn't.
caddyprofiledeps: It provides the deps of caddy. Switch to
switch-softwaretype leads to the error like "ImportError: No module
named furl". Force caddyprofiledeps installed first can solve this
issue.

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 nexedi/slapos!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