Upgrade Mineralogy 1.10.2 release CI/CD

[SkyBlade1978]

Summary

• align the Mineralogy 1.10.2 branch with the simplified multi-target release process
• modernize build, wrapper-validation, CodeQL, artifact-audit, and read-only tag-validation workflows with pinned Actions
• stage and verify the exact released OreSpawn 4.0.6.110021 dependency so CI does not depend on CurseMaven availability
• restore the project badges and branch-specific Build, test, and audit status badge in the README

Release safeguards

• produces only the three expected Mineralogy 6.0.1.110021 release jars plus SHA256SUMS
• keeps tag validation read-only; this PR does not create a tag or start publication
• does not change the Mineralogy version, OreSpawn requirement, gameplay code, schemas, changelog, or published releases

Validation

• clean tests, build, Javadocs, dependency verification, exact artifact audit, checksums, and Eclipse production-classpath checks passed
• two clean release builds produced identical hashes for the main, sources, and Javadoc jars
• actionlint 1.7.12 passed all changed workflows
• hosted Build, test, and audit: https://github.com/SkyBlade1978/MinecraftMineralogy/actions/runs/32790222272
• hosted Gradle wrapper validation: https://github.com/SkyBlade1978/MinecraftMineralogy/actions/runs/32790222075
• hosted CodeQL analysis: https://github.com/SkyBlade1978/MinecraftMineralogy/actions/runs/32790222082

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.