add inotifix explicitly in eggs target of stack/erp5 so that generated python2.6 script can load slapos.cookbook.

Decreasing tic interval increase reativity in case of few nodes.

Forcing modification of ERP5 internal configuration is not trustable for
production system (where custom configuration may have been applied by
administrator).

Instead, use erp5_promise bt5 which warn the administrator that the
configuration is not the expected one.

This settings seems commited twice in the same instant. See below:
http://git.erp5.org/gitweb/slapos.git/commitdiff/91c5be126a31c815407df1b2b2d5507cb6266bdd
http://git.erp5.org/gitweb/slapos.git/commitdiff/93ed854318acd93c1e735094d77a7b4b1c9bf82d

If present it will be used instead of /

It can be formatted with %(site-id)s in order to put site id there.

If added all country-code, email, state, city and company are required and are
later passed to certificate authority configuration.

Keep them simple, as section keys are local.

Make ssl-authentication really optional.

By configuring in JSON ssl-authentication to true for backend it will turn
listening apache to SSL based authorisation system.

SSL authorisation on such entry point is obligatory.

In order to follow typical ERP5 configuration SSL_CLIENT_S_DN_CN will be
passed as REMOTE_USER to Zope backend.

ERP5 CA is used to validate certificates.

This reverts commit 240cf0de.