Add persistent cache for toolchain auto-detection mechanism

[vmadalin]

Context

The Daemon toolchain auto-detection mechanism is part of Phase 1 of toolchain support for Gradle Daemon, where the motivation behind it and other technical details can be found on the public spec document. This PR implements the persistent cache for the toolchain auto-detection mechanism by adding indexed cache on CachingJvmMetadataDetector storing the JvmInstallationMetadata resolved object based on toolchain installation path. This cache is a VersionStrategy.CachePerVersion allowing to have a separate cache instance for each Gradle version that are stored under Gradle User Home directory.

Testing

Unit tests:

• CachingJvmMetadataDetectorTest.groovy
• InvalidJvmInstallationCacheInvalidatorTest.groovy

Integration tests

• CachingJvmMetadataDetectorIntegrationTest.groovy
• InvalidJvmInstallationReportingIntegrationTest.groovy
• DaemonToolchainIntegrationTest.groovy

Demo

Simple demo exposing how persistent cache for toolchain auto-detection mechanism works:

persistent.cache.toolchain.auto-detection.mov

Contributor Checklist

• Review Contribution Guidelines
• Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
• Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
• Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
• Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
• Provide unit tests (under <subproject>/src/test) to verify logic
• Update User Guide, DSL Reference, and Javadoc for public-facing changes
• Ensure that tests pass sanity check: ./gradlew sanityCheck
• Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If you don't want the stale bot to close it, then set a milestone for it.

[vmadalin]

Closing PR since this was created directly on Gradle gradle#28966 after addressing merge conflicts with partially merged Daemon toolchain implementation in 8.8