ADFA-4128: state the daemon-timeout rationale without a benchmark multiple

The Gradle daemon idle-timeout comment quoted a speedup multiple, which put a
benchmark figure into shipping production code. The reason the timeout is
generous is structural - a warm daemon skips the cold start, which dominates a
short rebuild - so the comment now says that instead.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Kj9YeCDHGp9DU8LPtfWJ7W

Author: fryanpan

app/src/main/java/com/itsaky/androidide/services/builder/HighPerformanceStrategy.kt

@@ -12,9 +12,10 @@ object HighPerformanceStrategy : GradleTuningStrategy {
 	const val GRADLE_METASPACE_MB = 384
 	const val GRADLE_CODE_CACHE_MB = 256
 
-	// 6GB+ devices can afford a generous timeout (warm daemon ~= 6x faster
-	// builds). 2h instead of Gradle's 3h default so the value is provably ours
-	// in the daemon log, while still outliving any realistic editing pause.
+	// 6GB+ devices can afford a generous timeout: a warm daemon skips the
+	// cold start, which dominates a short rebuild. 2h instead of Gradle's 3h
+	// default so the value is provably ours in the daemon log, while still
+	// outliving any realistic editing pause.
 	const val GRADLE_DAEMON_IDLE_TIMEOUT_MS = 2 * 60 * 60 * 1000
 
 	const val GRADLE_MEM_PER_WORKER = 512