Use a mod-specific Maven group for Mineralogy

[SkyBlade1978]

Summary

• change the unpublished Mineralogy 1.15 Maven coordinate from zone.moddev.mc:Mineralogy:6.0.1.115021 to zone.moddev.mc.mineralogy:Mineralogy:6.0.1.115021
• generate and parse the publication POM during check, failing unless its group, artifact and version are exact
• run the same coordinate guard before every remote Maven publication
• audit the main jar's Maven-Artifact manifest entry and extend the workflow contract tests

Why

The MMD Maven convention gives each mod its own group namespace so future loader-specific artifacts can sit beneath it without sharing the organisation-level artifact directory. Mineralogy 1.15 has not been published, making it a clean boundary for adopting the mod-specific namespace. Existing Mineralogy 1.10 through 1.14 and OreSpawn releases remain untouched.

Artifact impact

The public filenames remain exactly:

• Mineralogy-6.0.1.115021.jar
• Mineralogy-6.0.1.115021-sources.jar
• Mineralogy-6.0.1.115021-javadoc.jar

The sources and Javadoc jars are byte-identical to the merged baseline. The main jar differs only in the intentional Maven-Artifact manifest value; its other 9,268 entries are byte-identical.

Validation

• red-to-green WorkflowContractTest coverage
• 36 tests passed across six suites with no failures, errors or skips
• complete clean build, Javadocs, exact OreSpawn dependency, release artifact and checksum audits passed
• generated POM verified as zone.moddev.mc.mineralogy:Mineralogy:6.0.1.115021
• prepared immutable bundle verification passed
• dry publication task graph proved the POM guard runs before Maven publication without contacting the live repository
• ForgeGradle Eclipse generation, run isolation and production-classpath verification passed

No gameplay, Java API, schema, mod ID, version, CurseForge configuration, OreSpawn dependency, changelog, tag or release is changed.