Release OreSpawn 4.0.8 for Forge 1.10.2

[SkyBlade1978]

Summary

• release OreSpawn 4.0.8.110021 for Forge 1.10.2
• preserve all eight host/tag/biome editor fields beyond 32 characters and prevent silent truncation when reopening and saving profiles
• migrate the build to ForgeGradle 7 with reproducible main, sources and Javadoc release artifacts
• add the target-aware CI/tag-start workflow, release checksums and exact artifact audits
• keep API 1, schemas 4/6/5, registry/profile compatibility and consumer range [4.0.6,5.0.0) unchanged
• remove stale ForgeGradle 2 Eclipse GradleStart launchers during Buildship synchronization

This addresses the Forge 1.10.2 part of #243; the issue remains open for the other targets.

Validation

• 148 tests across 37 suites, with zero failures or errors
• OS1/OS3 ABI, Mineralogy/Sylvester migration, and surface/dynamic-fluid fresh/reload gates pass
• two clean release builds are reproducible and the exact three public artifacts are audited
• Eclipse Gradle refresh reports zero errors; the canonical runClient.launch reached the Minecraft 1.10.2 menu and exited without a crash report
• disposable packaged server/client/Sylvester checks and fixed-seed worldgen gates pass
• fork CI, CodeQL, and Gradle-wrapper validation pass on exact commit ded7c3550e33b70cf11d0155cc786a2b7a58d108

Release artifacts

• OreSpawn-4.0.8.110021.jar
• OreSpawn-4.0.8.110021-sources.jar
• OreSpawn-4.0.8.110021-javadoc.jar

API and deobfuscated jars remain development-only and are not published.

Publication boundary

This PR prepares the target branch. It does not create a tag or publish to Maven, CurseForge, or GitHub Releases.

[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.