Support object-based API calls to objain a recipe

[christianlupus]

Currently, we are transferring most data as strings, arrays, or comma-separated lists of strings when a recipe is to be transferred.

This should be replaced with an object-oriented approach, where text-based transmission is discouraged. So instead of having a recipeInstructions array with multiple strings, we should have an array with multiple Text objects or even HowToSteps. Similar for all other entries.

That will allow extending the Frontend in a separate step to allow for additional per-step images (#47, #324), videos (#206, #315), and other features.

I suggest adding an optional query parameter view to the GET call of /api/recipes/{id}. This can default to a legacy output to be consistent with the current way of formatting things. A new modern (or even v1, object, or similar) will allow switching to the object-based view of the recipes.

---

Depends on #1110

[github-actions]

This PR/issue depends on:

• [Batch] Updated parsing routines for recipes and output #1110
  By Dependent Issues (🤖). Happy coding!