Play Framework

fix: pin bundle frameworkPath so it stays distinct from application.path

For self-contained bundles, the play jar lives at
<appRoot>/framework/play-X.jar, which makes Play.init's auto-detect
(jar.getParentFile().getParentFile()) collapse Play.frameworkPath onto
application.path. The collision corrupts VirtualFile.relativePath() —
every app file ends up tagged with the {play} prefix — so precompiled
template lookup fails at startup with NoSuchFileException on
"from_play/conf/routes". Dev mode is unaffected because the framework
jar lives outside the app dir.

Fix: bundle-play.sh passes -Dframework.path=\$SCRIPT_DIR/framework, and
Server.main reads it and pins Play.frameworkPath before Play.init runs.
This keeps dev-time and dist-time path encodings consistent.

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