disable gradle daemon by default [LUCENE-9232]

We should disable the gradle daemon by default: the user can opt-in by changing the properties file.

If you forget to do this, you end out with leaked JVMs everywhere. It won't just leak one daemon, it will leak multiple ones.

I ran `ps` on my laptop, surprised at 13:00 to find 2 leaked gradle jvms when I hadn't used the thing since 07:00.

---
Migrated from [LUCENE-9232](https://issues.apache.org/jira/browse/LUCENE-9232) by Robert Muir (@rmuir), updated May 15 2020
Attachments: [LUCENE-9232.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-9232/LUCENE-9232.patch)

Start by locating the Gradle properties file that controls daemon behavior and review how the current default is configured. Done means the daemon is disabled by default while users can still opt in by changing the properties file; verify the build continues to work without leaked JVM processes.

Written by the indexing model from the issue text.