DEPRECATED Delete automated recipe

Deprecated: use DELETE /api/v3.1/automated-recipes/{recipe_id}/. This version stays available until it is switched off; see Moving recipes to v3.1.

When the recipes service fails, this version answers 500 with an HTML page, and an error in the 4xx range can arrive with a body that is not JSON. It also repeats the request to the recipes service up to three times, create included, so a create can run twice. v3.1 does neither: every error is {code, message, details}, and a request is repeated only when it provably never reached the service.

Permanently deletes an automated recipe. This is a hard delete and it cannot be undone: the SQL views the recipe produced are dropped, its cells and configuration are removed, the data tables it created in the workspace are cleaned up, and the intermediate recipes it was built on are deleted with it.

The cascade follows the recipes this one reads from, not the ones that read it: a recipe built on top of this one is left in place and will break, and an intermediate recipe that another deployed recipe also reads is deleted just the same.

Deleting frees the template slot. One recipe per template per workspace is enforced on create, so after a delete the same template can be deployed again - which is how a failed deployment is retired, and how a recipe whose account set has to shrink is replaced, since configuration is append-only.

Returns 204 with an empty body. The 204 says the deletion was attempted, not that every recipe in the tree went away: they are deleted one by one and a per-recipe failure is logged rather than reported here. Before deploying the same template again, confirm with GET /api/v3/automated-recipes/?template_id= that nothing is left.