Remove the CT Ingredient Wrapper

[TechLord22]

What

This PR removes the CT Ingredient Wrapper for recipes, instead converting the provided CTRecipeBuilder input directly to GTRecipeInputs. This will prevent future bugs with CT-specific behavior we would otherwise be unaware of, and also defines the behavior of all input scenarios CT can provide. This will us to choose which configurations we support.

As of this PR, items used in recipes with NBT will match any items that contain all of the recipe's NBT. As long as the sample completely overlaps with the recipe, matching will succeed. More complex matching can be achieved with GroovyScript instead, if desired.

For inputs representing multiple items, typically produced using CT's | operator, the NBT for each stack ORed together will be matched for exclusively the stack it applies to. See the validation section for details.

Validation

Using the following script, simple validation of this behavior can be performed.

<recipemap:assembler>.recipeBuilder()
    .inputs(<minecraft:dirt>.withTag({RepairCost: 0, display: {Name: "MyName"}}))
    //.inputs(<minecraft:dirt>.withTag({display: {Name: "MyName"}}))
    //.inputs(<minecraft:dirt>.withTag({display: {Name: "MyName"}}) | <minecraft:stone>.withTag({RepairCost: 0}))
    .outputs(<metaitem:dustSilver>)
    .duration(20).EUt(30).buildAndRegister();

Renaming dirt in the anvil to MyName will allow testing this the easiest, leaving only one input line uncommented for each of the following scenarios:

• With the first input line, the renamed dirt will match the tags exactly.
• The second input line will match the renamed dirt as well, as it contains all of the required tags.
• The third input line can be tested with /give @p minecraft:dirt 64 0 {display: {Name: "MyName"}} and /give @p minecraft:stone 64 0 {RepairCost: 0}. Both of the stacks for the third case match one of the valid input ingredients.

Outcome

Removes the CT Ingredient Wrapper to prevent undefined behavior. Supersedes #1604, and also fixes #1600.

Potential Compatibility Issues

No compatibility issues are expected other than those outlined above, which are now considered invalid input configurations.

[PrototypeTrousers]

looks good to me

[LAGIdiot]

Implementation looks reasonable. Ingame test was not performed.