Fix the hosted Java selector for Forge 26.1.2 releases

[SkyBlade1978]

Summary

• keep java_toolchain_version=25.0.3+9 as the exact Temurin compiler/runtime identity
• add java_setup_version=25.0.3+9.0.LTS, the catalog selector required by actions/setup-java
• add a regression contract that requires both values and prevents them being conflated

Cause

Release run 33652895504 routed and validated 4.0.16.2601021 correctly, then failed before Gradle started because GitHub's Temurin catalog exposes this build as 25.0.3+9.0.LTS, not the shorter 25.0.3+9 selector.

The shared dispatcher already supports a separate hosted setup selector. This target-specific metadata change leaves deploy-release.yml and the established Java 8, 16, 17, 21, and other branch release paths unchanged.

Validation

• ReleaseWorkflowContractTest passed under the isolated pinned Java 25 toolchain
• verifyReleaseConfiguration passed
• automatic JDK detection and download were disabled during validation
• git diff --check passed
• the failed release created no tag and did not enter Maven, CurseForge, or GitHub publication

No production source, gameplay behavior, API/schema, artifact name, or release content changes.