groovy

Use `File`s instead of `URI`s in `ClassLoaderFactory` API

It involved a lot of needless conversion, and we need a full `ClassPath`

to be able to do hashing later on.

+review REVIEW-6020

Moved int tests from open api to ui projects and changed them to bolt directly onto the ui implementation.

Removed GradleRunnerFactory from openApi.

Moved GradleRunnerTest from openApi to ui projects and changed it to bolt onto the ui classes directly.

Push a GradleDistribution into GradleExecuters so that they can adapt to different versions that they might be running.

Required some restructuring of the GradleDistribution hierarchy, and includes some extra tidy up.

Rename “GradleDistribution” to “GradleBuiltDistribution” and “GradleBasicDistribution” to “GradleDistribution”.

Use BasicGradleDistribution through the testing infrastructure, not GradleDistribution.

Don't have the GradleDistribution be responsible for providing the working space for a test.

Moved code related to GradleExecuter and GradleDistribution into org.gradle.integtests.fixtures.executer - Affects many, many files, but mostly just imports - Certain files (eg RuleHelper) are not in the correct spot, but were moved to avoid cycles

Another attempt at taming test logging.

I chose to duplicate some of LogbackLoggingConfigurer instead of refactoring for reuse as I'm not confident in changing LogbackLoggingConfigurer and the requirements are slightly different for testing.

The intention was to use a test rule to reset the logging before each test. There's some awkwardness with this in that some of the logging comes from other rules, which may run before the logging reset rule. This means that rules that emit logging need to explicitly reset logging before doing so.

A better approach might be to have a baseline logback.xml on the classpath and then reset the configuration _after_ each test (in case it fiddles with the config).

Attempt at using LogbackLoggingConfigurer to quieten the logging during test execution.