Move the files to update configuration to `JavaTestProject` This allows us reusing the configuration for both performance tests, and the Gradle Profiler. The `performance.scenarios` file will reuse the same files. There are 2 categories of files to change for now: `assemble` and `test`.
Fix test performance comparison We were running the `largeJavaMultiProject` with `max-workers=4` and `maxParallelForks=4`, which lead to each project spawning 4 test workers (for only 100 tests) and thus blocking all other projects from testing. Instead, we now use `maxParallelForks=1` for this scenario, which is much more realistic for a build that has lots of projects with only a few tests each.
We were measuring the time it takes Gradle to clean the output folder while Maven didn't do that work (as it has no concept of incremental builds). We now don't measure the clean time in any case.
We were comparing `gradle assemble` (which does no tests) with `mvn package` (which runs unit tests). We now explicitly exclude tests for Maven.