Reading of the release version and description is configuration cache compatible

[tylerbertrand]

Add release notes to githubRelease body

• Leverage Provider.fileContents() to support configuration caching when reading release notes file

Use configuration-cache-compatible Provider API to read version file

• Use configuration-cache-compatible Provider.fileContents() to read version file

Tests

1. Run ./gradlew clean build and inspect jar versions

gradle-enterprise-build-validation-scripts % find . -name *.jar
./gradle/wrapper/gradle-wrapper.jar
./components/fetch-build-scan-data-cmdline-tool/build/libs/fetch-build-scan-data-cmdline-tool-2.3.6-all.jar
./components/fetch-build-scan-data-cmdline-tool/build/libs/fetch-build-scan-data-cmdline-tool-2.3.6.jar
./components/configure-gradle-enterprise-maven-extension/build/libs/configure-gradle-enterprise-maven-extension-2.3.6.jar
./components/capture-build-scan-url-maven-extension/build/libs/capture-build-scan-url-maven-extension-2.2.2.jar
./buildSrc/build/libs/buildSrc.jar
./build/scripts/maven/lib/maven-libs/configure-gradle-enterprise-maven-extension-2.3.6.jar
./build/scripts/maven/lib/maven-libs/common-custom-user-data-maven-extension-1.11.1.jar
./build/scripts/maven/lib/maven-libs/gradle-enterprise-maven-extension-1.16.6.jar
./build/scripts/maven/lib/export-api-clients/fetch-build-scan-data-cmdline-tool-2.3.6-all.jar
./build/scripts/gradle/lib/export-api-clients/fetch-build-scan-data-cmdline-tool-2.3.6-all.jar

2. Execute dry run githubRelease

> Task :githubRelease
:githubRelease [This task is a dry run. All API calls that would modify the repo are disabled. API calls that access the repo information are not disabled. Use this to show what actions would be executed.]
:githubRelease [CHECKING FOR PREVIOUS RELEASE]
:githubRelease [CREATING NEW RELEASE 
{
    tag_name               = v2.3.6
    target_commitish       = main
    name                   = 2.3.6
    generate_release_notes = false
    body                   = 
        - [NEW] TBD
    draft                  = false
    prerelease             = false
}]

3. Modifying version.txt results in a new configuration cache entry being stored, and the dry run githubRelease uses the updated version.
4. Modifying changes.md does not result in a new configuration cache entry being stored as it is read lazily.
5. Running with no changes results in the configuration cache entry being re-used.