Play Framework

fix: forward conf-declared javaagent/agentlib to forked JVMs (PF-92)

PF-90's Python-CLI removal accidentally dropped the launcher's habit of
lifting `javaagent.path` and `agentlib` from conf/application.conf onto
the spawned JVM's command line. The framework's own conf parsing runs
after the JVM is up, so those keys (which are JVM-level flags, not
in-process config) get silently ignored under 1.13.x — tools like JaCoCo
produce no coverage data when the agent is declared via
`%test.javaagent.path=bin/jacocoagent.jar`.

Reintroduce the lift in Play1Plugin.kt with %<playId>. prefix priority
matching how Play resolves config at runtime. registerPlayJvmTask covers
playRun/playTest/playPrecompile/playEvolutions; PlayAutotestTask covers
its custom Play.server fork.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>