[DRAFT - don't merge] - making CookingRecipe extensible

[Archina]

This is my very first draft of changes, which I want to serve as a basis for feedback from modders and maintainers.

I tried to split the original Cooking Recipe into 4 classes to grow my own understanding of the routine and also to show how this could be used to register a set of different CookingRecipes with different logic sets that are identified through the code string.

At the moment CookingRecipe has to registered manually and this change would require to register the recipes under either essentials or survival as the following:

api.RegisterCookingRecipe("porridge", typeof(PorridgeCookingRecipe));
api.RegisterCookingRecipe("meatystew", typeof(StewCookingRecipe));
api.RegisterCookingRecipe("vegetablestew", typeof(StewCookingRecipe));
api.RegisterCookingRecipe("soup", typeof(SoupCookingRecipe));
api.RegisterCookingRecipe("jam", typeof(JamCookingRecipe));

Sadly I have troubles compiling and trying to run this on my machine, I have however worked under the following assumptions:

RegisterCookingRecipe registers the class so that worldForResolve.CookingRecipes can retrieve the matching class.

---

Current concerns:

• Too much messy inheritance stuff.
• I would prefer separating the CookingRecipe logic altogether from the CookingRecipe class by maybe introducing a CookingRecipeLogic - I have not done so because I wanted to keep the changes low and because I would then also have to rewrite RegisterCookingRecipe.
• I removed the interface ICookingRecipeNamingHelper that didn't seem necessary any longer, this may however be false or collide with other changes that are made to the game.