If slaprunner itself was installed on a slapos which had shared parts
enabled, these shared parts will also be used while installing softwares
inside the slaprunner.

Because ${buildout:shared-part-list} is a multi line property, it was
not possible to generate .cfg files (which needs special handling of
multi-line strings) directly from software buildout (where jinja
templates are not yet available), so we use a trick of generating a
plain text file in software and parsing it during instance.

Set default pidfiles for slapos node software and slapos node instance
command so that when they are executed they use by default the same
pidfile that are used by slaprunner GUI ( the green "play" button ).

This prevents potential problems with running slapos twice and fixs the
problem that default pidfile ( /opt/slapos/slapgrid-sr.pid ) is not writable.

This required slapos.toolbox 0.50

Conflicts:
	software/slaprunner/common.cfg

Conflicts:
	software/slaprunner/instance-runner.cfg

Conflicts:
	software/slaprunner/instance-runner.cfg

Conflicts:
	software/slaprunner/common.cfg
	software/slaprunner/instance-runner.cfg

rename of the template slapos.cfg.in to respect the standards