Fix Forge 47.4.10 compatibility and multiblock dispatch ownership

[Barbatosishere]

Summary

Adapt the packaged pattern provider for the 1.20.1 Forge 47.4.10 target and the AE2LT/Thunderbolt beta4 API while preserving input and output ownership across multiblock dispatch failures.

Changes

• Fix the server resource-reload listener to wait for the preparation barrier before invalidating recipe bindings.
• Harden dispatch confirmation, partial insertion compensation, exception ownership, and power-cost accounting.
• Improve persistent return-inventory saving and Occultism ritual output ownership, baselines, and AUTO/OFF lifecycle handling.
• Add validated wireless connections for block-only Occultism spirit-fire targets and keep client-only mixins out of dedicated-server loading.
• Update compatibility adapters and reflection mutation handling for Botania, Draconic Evolution, Malum, Mystical Agriculture, Avaritia, and related multiblock integrations.
• Add optional recipe conditions for Mystical Adaptations resources and regression coverage for reload, lifecycle, persistence, reflection, dispatch, wireless, and power behavior.

Testing

• Java 17, Forge 47.4.10: main worktree clean build passed and produced normal and slim JARs.
• 188 JUnit tests passed in the main worktree with optional runtime integrations disabled.
• git diff --check passed; the commit contains no build output, local dependency JARs, Thunderbolt source, or third-party JARs.
• The upstream clone could not complete an independent offline build because its Maven/ForgeGradle cache lacks the mapped AE2LT and related dependency metadata; no certificate-validation bypass was used.
• StablePatternProviderNbtMigrationTest remains excluded because it requires a deobfuscated AE2LT development artifact.
• Full in-game validation with every optional target mod was not available in this environment.