Play Framework

docs: purge pre-Gradle PLAY_PATH/ant guidance + PF-89 assessment (PF-90)

Three pages still described the Python-CLI setup that PF-90 deleted:

production.textile (EN + JA): drop the entire 'Deploying Without
Python' section. It told operators to use 'ant start -Dplay.path='
when no Python interpreter was available — the new shell wrapper
is shell + gradlew, no Python ever, so the section is meaningless.

ide.textile (EN + JA): rewrite the 'Custom configuration' section.
The old text walked users through manual classpath wiring with
\$PLAY_PATH/framework/play-\$version.jar, \$PLAY_PATH/framework/lib/,
and -javaagent on play.jar. With the Gradle plugin all of that is
derived from build.gradle.kts; any IDE that speaks Gradle imports
the project natively. New text points users at Buildship/VS Code's
Gradle support and gives a ./gradlew :playRun fallback for plain
text editors.

documentation/assessments/PF-89-junit-6-upgrade.md: removed. It
referenced framework/pym/play/commands/test.py and autotest.py
paths that no longer exist, and the assessment work it documented
is long since shipped (1.12.40). Frozen-in-time analysis docs add
no value once the implementation is in main; release notes carry
the historical record.

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