Gradle

+review REVIEW-6526

* origin/release:

Revert "Add 'enabled' information to the Finalize Build Cache Configuration Build Operation."

Handle progress events without message (#1988)

Use /cache instead of /build-cache in build cache sample urls.

Remove another reference of append=false for JaCoCo tests

Use a configure task to add jvmArgs to Test

Polish documentation for normalization

Pass immutable normalization strategies object

Remove MetadataFilter

Fix formatting of bullet list

Add release notes for JaCoCo and build cache

Reword the clean-up strategy for the local build cache

Add 'Origin' header to TeamCity REST calls

Add release notes about parallel download of dependencies

Defensive copy of broadcasters for removal

+review REVIEW-6520

This method was an attempt to workaround problems accessing protected methods, but the generated lookup will

always be `DefaultServiceRegistry` and won't grant access to protected methods of subclasses of the registry.

As a consequence, method handles are only used on public accessible methods. It's worth noting that we should

probably make the contract for providers stronger, since calling `setAccessible(true)` will not be possible

anymore in JDK 9.

Introduce improvements to the Finalize Build Cache Configuration Build Operation

This commit adds caching of the factory element type: it was always recomputed, which is actually very expensive.

So far, service methods were invoked through reflection. However, for each service, we could call `getGenericParameterTypes` several times

(for example, if the same service is created multiple times, typically project scope services), and we wouldn't cache the result of this

method call, whatever cost it has.

The `RelevantMethods` class now wraps the `Method` used in services into a `ServiceMethod` object that can be used for invocation. This

service method class has 2 possible backends:

- a method handle based backend, which should be faster than reflection because access check is going to be performed only once for all

- a reflection based backend, which is used as a fallback

Instead of passing around the mutable configuration for resource

normalization we create an immutable container for the

normalization strategies and use this instead.

+review REVIEW-6520