Don't use Gradle build and configuration cache for releases (#662)

* Don't use Gradle build and configuration cache for releases

- don't enable Gradle build and configuration cache for the project, but recommend it for the developer
- explicitly enable Gradle build and configuration cache for CI test jobs
- let AboutLibraries generate lib definitions itself again
- also don't archive test results (sometimes fails and we never use the results)

* Add encryption key for gradle cache

* Only warn on configuration cache problems (caused by AboutLibraries)

gradle.properties

@@ -3,12 +3,17 @@ org.gradle.daemon=true
 org.gradle.jvmargs=-Xmx4g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 -XX:+UseParallelGC -XX:MaxMetaspaceSize=512m
 org.gradle.parallel=true
 
-org.gradle.configuration-cache=true
-org.gradle.configuration-cache.problems=warn
-
-# https://docs.gradle.org/current/userguide/build_cache.html
-org.gradle.caching=true
-
 # Android
 android.useAndroidX=true
 android.enableR8.fullMode=false
+
+
+# It's recommended to add these settings to your $GRADLE_USER_HOME/gradle.properties:
+
+# org.gradle.configuration-cache=true
+# org.gradle.configuration-cache.problems=warn
+
+# https://docs.gradle.org/current/userguide/build_cache.html
+# org.gradle.caching=true
+
+