Remap IDs

1.3.1

Fixed

• Modded registry IDs not remapped on NeoForge (#5, #6) — On NeoForge 1.21.1, mods are constructed before vanilla bootstrap, and bootstrap freezes the builtin registries before any RegisterEvent fires. The MappedRegistry.freeze() hook therefore ran against vanilla-only registries: wildcard patterns matched nothing, modded targets (including KubeJS-created IDs) were "not found", and aliases injected for modded source IDs were clobbered when the real entry registered later. Finalization and alias injection are now triggered from FMLLoadCompleteEvent (mirroring the Forge 1.20.1 fix from 1.3.0), which fires after GameData.freezeData() when all mod content is registered. This also fixes wildcard remaps for modded item/block IDs.
• Recipe re-keying could overwrite existing recipes (#5) — Re-keying a recipe ID to a target that already exists (e.g. an entry without a types filter remapping aether:skyroot_stick → minecraft:stick while a minecraft:stick recipe exists) silently replaced the existing recipe. Colliding re-keys are now skipped with a warning, on all loaders.

Changed

• Entries without a types filter no longer attempt registry aliases for registries that don't contain the target — a typeless item remap previously produced "target not found in block/fluid/entity_type registry" warnings and pointless alias attempts. A typeless entry whose target exists in no registry at all now logs a single warning instead.