Port OreSpawn 4.0.16 to Forge 1.21.11

[SkyBlade1978]

Summary

Ports the complete OreSpawn 4.0.16 campaign to Minecraft 1.21.11 / Forge 61.1.0 and updates the target identity to 4.0.16.121111.

This carries the accepted fixes for:

• long Ore and Fluid editor values surviving open/save cycles;
• provider-declared natural terrain replacement ordering and unsafe-source protection (Residual vanilla Dirt survives total-conversion terrain replacement #255);
• Stable Layers rock bounds using actual world Y;
• dynamic biome registry weights and managed-ore filters ([1.18.2] Geome ID fallback drops biome-dictionary weights for dynamic biomes #262 and [1.18.2] Ore biome filters reject dynamic-registry biomes by object identity #263);
• public sampler height alignment ([1.18.2] GeologySampler disagrees with generated geology at 3D biome seams #266);
• provider biome-filter API parity and namespaced geome IDs ([1.18.2 API] OreDimensionDefinition.Builder cannot express supported biome filters #268 and [1.18.2] Creation editor rejects namespaced geome IDs in valid templates #269);
• exposed one-layer Snow and surface Ice conversion ([1.18.2] Dimension snow/ice material overrides do not convert loaded weather blocks #267);
• stable direct biome attribution shared by generation, sampling, and family-restricted ores;
• GameTest benchmark shutdown ownership.

Forge 61-specific adaptations retain Minecraft 1.21.11 Identifier, EventBus 7 registration, the target reload mixin, four access-transformer rules, merged Buildship output, the checksum-sealed zero-rule Mavenizer bootstrap, and exact packaged-runtime behavior.

The final Eclipse repair gives ForgeGradle's generated project disjoint bin/default, bin/main, and bin/test outputs, preventing Eclipse from rejecting nested build/sourceSets output folders. The generated classpath is now covered by a regression gate.

API major 1, schemas 4/6/5, registry IDs, existing provider fields, profiles, migrations, generated chunks, and compatibility range [4.0.6,5.0.0) remain compatible.

Validation

• 135 tests across 33 suites, with no failures, errors, or skips.
• 41 JSON/mcmeta files parsed; 16 locales with 359 matching keys; all 21 documents exported in parity.
• Full offline build, Javadocs, artifact audit, checksums, Buildship runs, and production Eclipse classpath checks passed.
• A cold exact-commit worktree reproduced all three release jars byte-for-byte.
• Empty-cache Forge 61 bootstrap used Java 25 and correctly required zero target compatibility patches; same-cache reruns were idempotent.
• Exact official-named Forge 61 packaged server fresh/reload and packaged client create/render/save/reload/editor tests passed with clean OreSpawn-attributable logs.
• Surface, natural-host, dynamic-biome, weather-material, fluid, sentinel, stable-attribution, preferred-seed, and benchmark lifecycle gates passed fresh and reload.
• The Eclipse-only follow-up left the main, sources, and Javadoc artifacts byte-identical to the fully qualified candidate.
• Exact candidate debcc79851436de6ac8ca6fbcc235889745295b1 was manually tested and accepted before publication to the fork.

No direct MMD branch update, tag, release, or issue closure is included in this PR.