As develop recipes have to be available *before* buildout run add check-recipe
part which will stop buildout in case if recipe is not in develop-eggs.

Fetch recipe using usual buildout commands to interact with buildout's provided
git.

installKeyAuthorisationApache is not reimplemneted.
Some lower level apache methods are required for reference.

Revert "Drop already implemented parts."

This reverts commit 4a8671fb.

Conflicts:

	slapos/recipe/erp5/__init__.py

Note: Not implemented in new way fronted code with required templates are left.

Missing file.

mysql has limit to 16 characters.

Allow to just request default profile. Set usual site id and by default lock
down backend access.

It allows provide to set some defaults.

Also use directly parameters instead of json.

Json would require in-code parsing, which would lead to complex recipes.

It will request all required services. json is in parameter dict.

More: software.cfg does not have to specify a lot of parts, as main template
is driving the choice process.

haproxy checks for site-id/getId response, but the site does not exists yet, so
it disallows to access the site.

In case of instantiating erp5 software type the later buildout will fail with
correct error message. But template is generated *always*, even in cases when
some data are not available yet.