Port OreSpawn 4.0.16 to Forge 1.20.6

[SkyBlade1978]

Summary

Brings the Forge 1.20.6 branch up to OreSpawn 4.0.16.120061, preserving Minecraft 1.20.6, Forge 50.2.0, Java 21, API 1, schemas 4/6/5 and existing world/profile compatibility.

Gameplay and compatibility fixes include:

• preserve long host, tag and biome-filter editor values;
• replace provider-declared natural terrain before later authored features, while protecting fluids, bedrock and block entities;
• evaluate Stable Layers rock bounds against actual world Y;
• resolve dynamic biome weights and ore filters through stable registry keys;
• align public sampling with generated surface height and direct quart-biome attribution;
• expose the existing provider biome include/exclude contracts and accept namespaced geome IDs;
• convert exposed one-layer Snow and surface Ice without touching buried/authored materials;
• keep GameTest benchmark lifecycle under the harness while retaining ordinary benchmark auto-stop.

The branch also moves Forge 1.20.6 to ForgeGradle 7/Gradle 9.6.1, deterministic version-only artifacts, isolated Mineralogy qualification, cold Forge bootstrap verification, current CI/CodeQL/wrapper workflows and the complete 21-document export. Forge 50 remains official-named with reobf=false.

Validation

• manually accepted packaged candidate;
• 134 tests across 33 suites, all passing;
• 40 JSON/mcmeta files parsed, 16 locales with 359 matching keys, and 21-document byte parity;
• offline clean build/Javadocs/artifact audit and Buildship Eclipse launch verification;
• exact packaged Forge 50 client plus fresh/reload server qualification;
• natural-host, low-world, dynamic-biome, Snow/Ice, sampler/family-attribution and benchmark lifecycle regressions green;
• empty-cache Forge bootstrap and same-cache rerun green with an explicit zero-rule Forge 50 manifest;
• matched worldgen performance remained below the 10% investigation threshold;
• feature-head CI, CodeQL and wrapper validation all passed.

No API-major, schema, registry ID, profile filename, migration behaviour or existing-chunk rewrite changes are included. No version bump beyond the planned 4.0.16.120061 identity is needed.