Play Framework

fix: revert SettingsParser second-regex widening (release 1.12.11)

1.12.10's SettingsParser hotfix correctly added optional classifier
support to the FIRST regex (org -> module rev) but eagerly mirrored the
change on the SECOND regex (module rev, no org). That second-regex
change had an unintended consequence: input "play -> play" — the
contains: entry the framework's own playCore repo uses to claim the
play artifact regardless of revision — started matching the second
regex with revision="->", because the optional 4th group made the
regex permissive enough to swallow the trailing " play" token.

The buggy module-configuration registration (org=play module=play
revision="->") never matches a real "play -> play 1.12.11" lookup, so
Ivy falls through to mavenCentral and reports "play not found".

Reverts the second-regex change; only the first regex needs classifier
support since native artifacts always have an organisation in our YAML.

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