rename certificate-authority software release and stack to caucase

This commit allow to use certificate authority stack in erp5 stack to
request apache certificate (in instance-balancer).
if this is enabled (parameter: "certificate-authority": {"enable": true, ...}
instance erp5 will request one more partition containing the CA, then publish the ca-url to balancer
Instead of generated self-signed certificate in balancer, certificate will be signed on CA.

The modification also allow to use the certificate in apache.conf for authentication (SSLVerifyClient require)
by default it True in erp5 stack, the parameter "balancer": {"ssl-client-verify": false} will disable it

- It's also possible to set a custom backend_path for each zope instance.
"zope-partition-dict": {"service": {"backend-path": "/%(site-id)s/portal_slap", ...}}
- If "ssl-client-verify" is false,
it will be possible to add "ssl-authentication": true in zope-dict which will enable authentication on a specific zope service.
Both features was customized in slapos-master sr, and was removed to be reimplemented in erp5 stack.

Makes it easier to deploy a functional replication setup.

They closed, and downloads get redirected to a wiki page.

Stop breaking this tool for everyone developping on slapos.

  Apache verbose way too much with LogLevel info

It was not working with wrappers to work around shebang length limitation.

https://bitbucket.org/sirex/rubygemsrecipe/issues/9/gem-shebang-line-length-limitation

  Allow set software-root via parameters allow the webrunner inside a erp5testnode,
  recover the the previous builds from previous resilient tests, and only update (instead build from scratch)
  This is a typical usage on the webrunner (keep updating SR), so there is no
  problem on use this approach on erp5testnode tests.

Use the same exclude patterns (receiving end may want to exclude a file set
different from the time backup was exported, or may have a different set of
buildout-managed files which would be dangerous and misleading to
overwrite).

Do not apply exclusions to unrelated paths ("project", "proxy.db" and
"etc").
Simplify global exclusion file generation.
Add support for absolute and partition-relative exclusion paths
(previously, only partition-relative were supported).
Pipe exclusion file to rsync, to avoid an intermediate disk write.
Remove some directory prefix duplication by using PWD-relative paths
(except in one place, for runner-import.sh.jinja2 comparison).

So avoid spawning "cat" only for this.
Also, variable expansion quoting.

More similar changes will come later as part of larger changes.
Also, fail if
  cd "$backup_directory"
fails, as it is supposed to exist by that point.

Imperfect: single-quote escaping would be good. But this at least makes
it significantly harder to accidentally end up outside variable assignment.
Users of these values will be added in a later commit.