in some rare cases, proxy was still alive for unknown reasons,
thus we had troubles to start a new one. some testnodes were failing
randomly because of this

parameters "develop = false" and "revision =" are now set every time

We have local repository to control which repository at which revision is tested.

Following @rafael advice on a related commit to slaprunner

    nexedi/slapos@c8c81baa
    nexedi/slapos!22 (comment 1780)

let's also leverage multicore when building NumPy- & Ruby- related
software under testnodes.

/reviewed-by @rafael, @seb  (on !23)

When testnodes are unable to create partitions and unable to find
runTestSuite command, this change avoid having the testnode always
trying to reuse same revision by forcing to move test result to failed

Take into account remarks done by Julien and Vincent.
Also stop using deletePycFiles for git repositories, git clean -fdx
is doing better (it remove more useless files if needed)

...in testERP5TestNode.

glob uses os.listdir, which returns list in arbitrary order.
Sometimes we have seevral partitions containing bin/runTestSuite. We want to use the one closest to the root instance (i.e alphabetical order, test0-1/bin/runTestSuite is better thantest0-3/bin/runTestSuite).

Usecase: webrunner, for which main instance contains a bin/runTestSuite for unit tests. But resiliency tests (dedicated partition, usually test0-0) also has bin/runTestSuite, and then requests a normal instance of slaprunner (usually test0-3).

  In this way we don't have to duplicate the method everywhere.

 The UnitTest were running on a different folder them expected, causing often erase of the selenium
 setup and others test folders. This were causing over compilation.

Eg, instead of 1, 6 and 12, it was being sorted as 1, 12 and 6 users.

This is required for report including Japanese characters as Bitstream
font (the default) does not handle such characters.

We only only need an usual test result proxy, we only need the additional
method getRunningTestCase

This commit in order to force the flush of files
containing test informations after each iteration.