software/slapos-testing: add back required versions pins

217f7f05 (slapos-testing: don't pin tested eggs, 2021-01-12) was wrong,
some versions needs to be pinned for initial installation of the software.
The problem was not visible when the software was already installed and
updated in place, but when installing software from scratch, it was failing
very early with an error like:

    While:
      Bootstrapping.
      Getting distribution for 'slapos.libnetworkcache'.
    Error: Picked: slapos.libnetworkcache = 0.20

software/slapos-testing/software.cfg

@@ -203,22 +203,29 @@ output = ${buildout:directory}/template.cfg
 mode = 640
 
 [versions]
-# clear version pins of tested eggs, to make sure buildout always use the
-# git checkout version.
+# When possible, clear version pins of tested eggs, to make sure buildout
+# always use the git checkout version.
+# This is not possible for buildout extensions, or for buildout recipes
+# that are also used in this profile, so we keep version pins for these.
+# We need to keep the versions in the profiles (in stack/slapos.cfg, or
+# maybe here during development) in sync with the latest version from their
+# setup.py , because if the version in setup.py is newer from the version
+# pin, buildout will install the egg from pypi and run the test against
+# released egg
 caucase =
 erp5.util =
 kedifa =
 slapos.cookbook =
 slapos.core =
-slapos.libnetworkcache =
-slapos.rebootstrap =
-slapos.recipe.build =
-slapos.recipe.cmmi =
+# slapos.libnetworkcache =
+# slapos.rebootstrap =
+# slapos.recipe.build =
+# slapos.recipe.cmmi =
 slapos.recipe.template =
 slapos.toolbox =
 rubygemsrecipe =
 
-# All depencies should be pinned.
+# All other depencies should be pinned.
 Pygments = 2.1.3
 zc.lockfile = 1.4
 bcrypt = 3.1.4

[Julien Muchembled]

If, for example, there's a new release of slapos.recipe.build and it's not used yet by slapos.git (stack/slapos.cfg still refers to an old version) then it won't test the repository code.

Worse, and no idea why, it could still test an old version after stack/slapos.cfg is updated, e.g. https://erp5.nexedi.net/test_result_module/20210925-CABBAC0A/12 (search for paths in tracebacks).

(today, slapos.recipe.build fails due to a known bug in buildout that was hidden so far)