Allow custom multiblocks to have a custom CrafterComponent

[Luligabi1]

Problem

AbstractCraftingMultiblockBlockEntity implements CrafterComponentHolder, but directly accesses crafter instead of calling getCrafterComponent on tick, meaning any implementing classes are unable to have a custom CrafterComponent.

Solution

All direct accesses to crafter on tick are replaced by getCrafterComponent. This PR also includes a new method called onCraft that allows custom CrafterComponents to detect when a recipe is completed without overriding/mixin injecting tickRecipe.

Use case

Imagine a machine that alters the non-consumed input stack in some way (i.e. one of its data components' value). If said way is not recipe dependent, CrafterComponent is the most sensible place to modify it.

[Technici4n]

Oh so you're writing an addon? Is it public yet?

[Luligabi1]

Oh so you're writing an addon? Is it public yet?

Hopefully I can get it out this month 🙂