Report reason for Configuration Cache misses via an API

[joshfriend]

Expected Behavior

When there is a configuration cache miss, the reason is only reported in console output:

Calculating task graph as configuration cache cannot be reused because the set of Gradle properties has changed.

Gradle should have a lifecycle listener that reports these cache miss events and their reasons so they can be attached to build scans in the "Configuration" section of the "Performance" tab, or also to some custom telemetry service.

Current Behavior (optional)

No response

Context

With the current data collected by the Develocity plugin, I can analyze the hit rate for configuration cache, but am unable to diagnose the causes for cache misses.

[ljacomet]

This feature request is in the backlog of the relevant team and is prioritized by them.

---

Relates to:

• There is no reasonable way to see all invalidated configuration cache inputs #26440