Crafter Recipe Preferences for Conflicting Recipes

The Issue Here:

A Java data pack, a Java mod and a Bedrock addon can add new recipes. Sometimes, 2 recipes from multiple data packs or mods or even the same data pack/mod in Java, and multiple addons or even the same addon in Bedrock, causing a recipe conflict for shaped recipes if the exact ingredients arranged in an exact array is used by 2 or more crafting recipes. This is where Crafter Recipe preferences come in.

How it works as an example:

Say you have a Bedrock addon that adds a recipe that uses 9 iron ingots in the crafting table to produce a new item from an addon using the crafting_table tag, but that same recipe was already used by the iron block before. If you put the 9 iron ingots in a crafter, you may find that the crafter is biased to craft an iron block or the addon's item, with no control over the output due to recipe conflict. 
This is where the Crafter Recipe Preferences come in, configured per crafter. If the player or hoppers put 9 iron ingots into a crafter, the player can then decide if they want the iron block or their addon item to be crafted. The crafter will then remember which recipe to craft should it ever find a recipe conflict like this once more. 

Why it is useful:

For players who use mods, modpacks and/or many data packs in Java Edition, and for players who use multiple add-ons in Bedrock Edition, this will be helpful for players who want to automate production of many modded items / add-on items respectively in case of shaped recipe conflicts.