BEF 1.5.1 Feb 2022 Performance Fixes for Bazel JUnit Launcher

We had an internal use case in which a single Bazel package had a large set of java_test targets. This surfaced a performance issue in BEF experienced when launching tests. There would be a large delay before the tests started running. See Issue #381.

The problem was that the generated Eclipse JDT test classpath produced by BEF was adding the Bazel deploy jars from every test in the Bazel package. The deploy jars are large as they contain copies of all main and test classpath classes. Including them in the JDT test classpath bloated the classpath with many duplicated classes. This caused the launching of tests to be very slow.