We'll add monitoring to NEO so some parts are also moved there from ERP5.

  direct access fail on the new buildout.

  Rename --config to --configuration on apache-dex among others changes.
  This is just to reduce the diff between erp5 and slapos-master

This is a follow-up of commit 5c980caf,
now that the new code of the 'wrapper' recipe is used (1.0.58 released).

/reviewed-on nexedi/slapos!220

The slapos master use different instance-erp5 and instance-balancer than erp5 software release. So I included the monitor changes there as well to fix the issue 

/reviewed-on nexedi/slapos!189

  Apply commits:
   stack.erp5: Drop unneeded executable permissions. (fe7ea950)
   stack.logrotate: Fix support for stopped processes.
   stack.erp5: Use an iterator to produce port numbers.
   software/erp5: if wendelin-core-zblk-fmt is not given, then use wendelin.core's default.
   software/erp5 & stack/erp5: Add a new parameter wendelin-core-zblk-fmt.

  This changes were squashed into a single commit and it includes:

    - install slapos_configurator by default
    - Allow define ssl authentication for a certain zope family
    - Allow define custom zope path per zope family

  Those changes are originally written by Alain Takoudjou and rewrited by Rafael Monnerat

  The local changes are not yet generic enough to be shared among stack, so
  Introduce local changes here better

If the list of families does not change, their ports must not change, and it's
wrong to get this by relying on CPython implementation details. Even if we
automated the update of frontends with new urls, this couldn't be done
atomically and we'd get random failures.

Currently, frontends are only updated manually so we also want to minimize
changes when families are added/renamed/removed. By sorting alphabetically,
we have something predictable. Of course, this does not cover cases like the
following one:
- before: A, B, C
- after: A, C
Even if we added a 'port-base' parameter for the balancer, the port would
change for one of the 2 families.

We have no need for the moment, but we could go further with an optional list
parameter to choose the order, and a special value to skip ports. Another
option is to use publish-early but it's more complicated to implement and
we lose everything when we reinstanciate.

The sort in haproxy.cfg.in is for the stats page.

New 'slapos-kill' from slapos.toolbox is used instead of 'killpidfromfile'
This is required for NEO which does not write any pid file.

The inline recipe for ERP5 has been improved and converted into recipe,
which is reused for NEO.

Templates are instanciated only if they're used, so no need anymore to
wrap them with:

  {% if slap_software_type == software_type -%}
  ...
  {% endif %}

Move haproxy httpchk configuration per-listen as zope's webdav returns 401
on (at least) GET / . TCP-level checks are still active, which should be
sufficient.
Also, change zope_family_address_list check to getitem as it's more natural
than concatenating.
Also, stop using apache.zope.backend recipe to add support for per-port
scheme so automatic ERP5Site creation knows which URL is really HTTP.
Also, stop using certificate_authority recipe and call openssl directly
when generating self-signed cert for https/webdavs support.
Also, rework balancer parameters a bit (still undocumented).
Also, make instance-balancer always publish ipv6 value (empty when no ipv6
available), so instance-erp5 always succeeds.

Not perfect yet, as some strings end in configuration files for example
and need escape mechanisms aware of individual configuration file syntaxes.

Fixes backend maxconn value: it's now equal to zope's number of threads.
Instead, generate configuration file from template and wrapper from
stand-alone recipe.
One local-only feature is lost: haproxy-ctl command is not present, but its
usage should be rare enough to not be a problem now. Socket is present
anyway, so any tool able to access a unix socket would do (ex: socat).

Also, fix frontend request.

This work has nothing to do in erp5-component branch, and is preventing it
from being merged to erp5 banch more often.
Conflicts because of non-reverted
6d1a9805 have been resolved to that its
intent is preserved with non-cluster ERP5 SR.

This reverts commit 77976a14.
This reverts commit 7aa1d92c.
This reverts commit 80062015.
This reverts commit 36ed58f2.
This reverts commit 1fe3f466.
This reverts commit 7731726a.
This reverts commit eb2016c4.