somewhat improved cooking system

[lolman360]

About The Pull Request

new cooking system! heavily modular.

new things:
all cookable food is now a subtype of food/snacks/ingredient/ and stores its own cooking data (how long it takes etc).
all growns are now ingredients
all food can now stack! you can only stack cooked food with cooked food, etc. you may need different amounts for recipes now
some cookable food may have special effects if cooked via certain methods

food holders (saucepans, oven dishes, pots, skillets etc) are now used for making dishes. you can put a bunch of ingredients in them (currently unlimited, todo max capacity), cook them all at once and then serve the resulting dish via plates/bowls/etc

cooking machines exist. they just cook the food inside them. temperature settings are variable so you can cook food faster/slower if you like

recipes for hardcoded (non-modular) foods generally still exist. you still have to put the food all in a food_holder and cook it, but it will make the output item which you can then remove.
TODO:

• basic /ingredient type impl
• cooking machines basic functionality (IO, actually cooking stuff)
• food holders basic functionality (IO)
• reagent handling (via reagent temperature)
• food holders advanced functionality (serving dishes, identical ingredients increasing serving size instead of duping, dish autoname generation, etc)
• cooking machines tertiary functionality (cool sprites with overlays for food, etc)
• additional cooking methods (bonfire ✅ , welder ✅, supermatter ✅, hex piping, atmos burnchambers, etc)
• recipe handling
• sprites
• port old recipes and food over
• /snacks/ingredient/grown
• tgui recipe book
• recipe visualizer
• dishes getting dirty/ cleaning dishes

Why It's Good For The Game

new cooking system? delightful

Changelog

🆑
todo: CL
/:cl:

[github-actions]

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ two week, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself