Configure a RetryAnalizer to retry the non-deterministic test failures

This would allow us to configure the tests that fail in a non deterministic way in Jenkins to be retried automatically. Hopefully this could reduce the noise in our PR builders. This PR already configures the retry policy in one test known to fail randomly, but could be extended to other tests if this approach turns to be useful.

Note that with this change the retried tests will also show the failures in the output, but the build will be marked as succeeded if they succeed after the retry.

Inspired by: http://stackoverflow.com/a/18374673/3540564

/cc @demobox @adriancole 
This is to avoid an issue with the duplicate class finder. Scriptbuilder and core have this file in the test resources folder.