Alternative mechanism for detecting JUnit5

[LorenzoBettini]

As noted in org.pitest.pitclipse.launch.AbstractPitLaunchDelegate.isJUnit5InClasspathOf(IJavaProject) we use a naive mechanism for detecting JUnit5 on the classpath.

We could try to load some classes of the JUnit 5 engine by constructing a classloader using the classpath of the Java project.
Something like (untested)

String[] classPathEntries = JavaRuntime.computeDefaultRuntimeClassPath(javaProject);
List<URL> urlList = new ArrayList<URL>();
for (int i = 0; i < classPathEntries.length; i++) {
	String entry = classPathEntries[i];
	IPath path = new Path(entry);
	URL url;
	try {
		url = path.toFile().toURI().toURL();
		urlList.add(url);
	} catch (MalformedURLException e) {
		e.printStackTrace();
	}
}
URL[] urls = (URL[]) urlList.toArray(new URL[urlList.size()]);
URLClassLoader classLoader = new URLClassLoader(urls, parentClassLoader);

[LorenzoBettini]

Actually, it's much easier:

    public static boolean onClassPathOf(IJavaProject project, String fullyQualifiedName) throws CoreException {
        return project.findType(fullyQualifiedName) != null;
    }

[LorenzoBettini]

@echebbi I hope you don't mind I'm merging these PRs