Fix two bugs causing intermittent crafting failures when merging jobs with shared recipe dependencies

[Copilot]

When two crafting plans share a sub-recipe (e.g. both fences and doors needing planks, where planks are also needed for sticks), merging the duplicate plank jobs left dependent jobs orphaned and deserialized the dependency graph incorrectly on world reload.

Fixes

• Transfer dependents on job merge (CraftingJobDependencyGraph.mergeCraftingJobs): When mergeCraftingJobs(target, mergee, true) is called, the mergee's dependents (e.g. SticksJob which depended on the merged PlanksForSticks job) were never transferred to target. As a result, crafted output from target bypassed those jobs and flowed directly to network storage instead of their buffers, stalling the crafting chain. The fix transfers all graph-level and job-level dependent links from mergee to target before onCraftingJobFinished removes the mergee.

• Fix deserialization tag key (CraftingJobDependencyGraph.deserialize): The dependents map was deserialized from the "dependencies" NBT tag instead of "dependents", causing dependencies == dependents after every world load and corrupting crafting job routing on restart.

// Before (bug)
CompoundTag dependentsTag = tag.getCompound("dependencies");

// After
CompoundTag dependentsTag = tag.getCompound("dependents");

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.