Upgrade officially all SR to latest zc.buildout version.

repositories if configured are public. Thus such a check will by design fail.

@seb, @rafael  please review. I tested this and it works.

/reviewed-on nexedi/slapos!114

Then we'll upgrade setuptools for everyone at the same time as we switch to
zc.buildout 2.x

This solves the issue of accessing any file hosted by the apache in every test node when there is no IPv6 access for the client.

  Version up only goes to buildout2 case, buildout 1 series keep the same.

Conflicts:
	software/erp5testnode/software.cfg

86deb9c6 (*: slapos.git moved to https://lab.nexedi.com/nexedi/slapos.git)
went over whole tree and updated slapos.git URL but when changing
non-top-software.cfg-like files forgot to update their md5sum in
software releases.

Fixes started to appear - e.g. 8b1496c3 (kvm: fix md5sum, thanks
@alain.takoudjou), but generally the whole tree remains more-or-less
broken.

Fix it. (not tested - manually checked files and updated md5sums)

/reported-by @rafael

  The branch erp5testnode should not be a dependency for install a release.

No need to expose this slapproxy to the outside.

Explicitely list them, because develop egg doesn't not guarantee respect of dependencies.