Conditionally autolearned recipes

[I-am-Erk]

Problem

Autolearning recipes is currently a pretty simple matter. If the recipe is set to autolearn, you learn it when you meet the skill requirements.

A lot of the current "loot all the books" meta would become much more interesting if there were more complex ways to learn recipes.

Solution

Originally I was just going to ask for a field that required a proficiency before the recipe would autolearn, but then I thought of something way more cool and powerful.

Add an autolearn_conditional field, (edit: or maybe conditional_visibility) which uses the standard JSON conditionals (the ones originally designed for dialogue) to specify a set of conditions required to autolearn (or show, if we go with visibility) the recipe.

This would allow proficiencies, mutations, starting professions, time since cataclysm, current season, items in your possession, and an almost infinite number of other criteria to be required before you can learn a recipe. We'd be able to use and and or in those requirements, and basically do whatever we want to trigger access to particular recipes.

We should also add a forget_if_false option (edit: or hide_if_false if we use conditional visibility), which would cause you to lose the recipe if the conditional was no longer true. This would allow some really weird stuff, like having a snowball recipe that was only available in winter while outdoors.

Other Notes

We should consider using JSON conditionals in other contexts, such as determining when certain item actions are available. They're powerful and standardized.

[kholat]

Now this, is pod racing!

[Aivean]

Somewhat related: #45262

[Ramza13]

So once #42786 is merged this will be pretty easy to do.