Play Framework

fix: depend on compileJava before forking Play JVM (PF-94, release 1.13.9)

Without this, build/classes/java/main/ goes stale across edits to app/
sources because no Gradle task in the plugin's task graph rebuilt it.
PropertiesEnhancer's javassist ClassPool walks the runtime classpath in
order and finds the stale Gradle output before the freshly enhanced
bytecode in tmp/classes/, raising NotFoundException on any field added
since the last manual `gradle compileJava`. The headless playAutotest
flow surfaces this only as a generic FirePhoque exit=255 with the real
stack buried in logs/system.out.

Wire compileJava as a dependency for every task that forks the Play
JVM with sourceSets.main.runtimeClasspath on its classpath: playRun,
playTest, playPrecompile, playEvolutions (via registerPlayJvmTask),
plus playAutotest, playStart, and playRestart. UP-TO-DATE makes this
free when nothing changed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>