Fix 1.13.2 release artifact filenames

[SkyBlade1978]

Summary

• remove the redundant Minecraft-version prefix from the Forge 1.13.2 public archives
• produce OreSpawn-4.0.8.113021.jar plus the matching sources and Javadoc jars
• align the CI artifact upload paths with the multi-target release dispatcher
• extend verifyReleaseConfiguration so the exact public filenames and workflow paths cannot silently regress

Why

The 1.13.2 build retained its historical OreSpawn-1.13.2-... archive base name even though the fourth component of the current version already identifies Minecraft 1.13.2 Forge. The release dispatcher correctly expected the agreed version-only filename and therefore could not stage the build output.

Verification

• 123 tests passed across 31 suites
• full clean build, Javadoc, artifact, checksum and Eclipse production-classpath gates passed
• two clean release builds produced identical hashes for all three public jars
• prepared-publication artifact and Maven POM verification passed
• the exact renamed main jar passed packaged Forge client and dedicated-server qualification
• fork Build, test, and audit, CodeQL, and Gradle wrapper validation workflows passed

No version, gameplay, schema, API, tag or publication behavior is changed by this PR.