Play Framework

fix: release zip exec bits + playNewApp version sync + framework jar validation (release 1.13.3)

- Ant `package` now ships gradlew with the executable bit set (previously
  only `play` got filemode 0755), so unpacking the release zip on Unix no
  longer requires a manual `chmod +x` before `play new` works.
- Root build.gradle.kts derives `version` from framework/build.xml's
  baseversion instead of a hardcoded literal. playNewApp injects this
  value into generated apps' build.gradle.kts, so a version bump in
  build.xml now propagates everywhere automatically (the 1.13.2 zip
  shipped with frameworkVersion="1.13.0-SNAPSHOT" because the literal
  was never bumped — silent classpath dropouts followed).
- New `_playValidateFramework` task in Play1Plugin fails loudly when
  $frameworkPath/framework/play-<version>.jar is missing, listing the
  available alternatives. Wired as a dependency of extractPlayModules
  so every framework-consuming task (compileJava, playRun, playTest,
  playPrecompile, playBundle, ...) inherits it transitively. Replaces
  the previous "package play does not exist" wall of javac errors.

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