test/resilience: do not use shared build folder for both runners

as it creates compilation issues (both runners will try to compile
same component at same time)

software/erp5testnode/testsuite/instance-resilient-test.cfg.jinja2

@@ -50,11 +50,6 @@ config-resiliency-backup-periodicity = */10 * * * *
 config-resilient-clone-number = 1
 config-ignore-known-hosts-file = false
 config-cpu-usage-ratio = 1
-# Use one external folder (same of erp5testnode for build the software
-# This is a way to preserve the latest software release build speeding up
-# the tests.)
-config-software-root = ${buildout:directory}/../../soft
-config-buildout-shared-folder = ${buildout:directory}/../../shared
 config-no-ipv4-frontend = true
 
 # Use same repository / branch for the software installed in slaprunner

software/erp5testnode/testsuite/slaprunner.cfg

@@ -7,7 +7,7 @@ parts += template-erp5testnode
 
 [template-resilient-test]
 filename = instance-resilient-test.cfg.jinja2 
-md5sum = be4adbc196f07f5e39ca78401dfa53ec
+md5sum = 495bf2dacb3de66607a87a23d3765fa2
 
 # We have to use an extra level of indentation here because this is substituted
 # during software buildout to generate instance buildout, but the