Cache wrapper zips and generated jars individually

Using a single cache entry for all files of a type is necessary to avoid
overloading the cache service. However, this mechanism is not very efficient
for certain artifacts like wrapper zips and generated-gradle-jars, where the
same individual files are often shared between different jobs.

With this change, any configured file patterns that do not end in '*' will
be cached as individual files. At this time this includes downloaded wrapper
zips and generated-gradle-jars.

Fixes #78

.github/workflows/integTest-caching-configuration-cache.yml

@@ -45,8 +45,8 @@ jobs:
         arguments: test --configuration-cache
         cache-read-only: true
 
-  # Check that the build can run when no bundles are restored
-  no-bundles-restored:
+  # Check that the build can run when no extracted cache entries are restored
+  no-extracted-cache-entries-restored:
     needs: seed-build
     strategy:
       matrix:
@@ -55,11 +55,11 @@ jobs:
     steps:
     - name: Checkout sources
       uses: actions/checkout@v2
-    - name: Execute Gradle build with no cache artifact bundles restored
+    - name: Execute Gradle build with no cache extracted cache entries restored
       uses: ./
       with:
         build-root-directory: __tests__/samples/groovy-dsl
         arguments: test --configuration-cache
         cache-read-only: true
-        gradle-home-cache-artifact-bundles: '[]'
+        gradle-home-extracted-cache-entries: '[]'