DEPRECATED Check the extraction tables a recipe reads

Deprecated: use GET /api/v3.1/automated-recipes/{recipe_id}/extractions/. 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.

Reports the extraction tables the recipe reads and whether each one already exists in the workspace destination. Use it to decide when a build that failed for missing data is worth repeating: once every table_exists is true, the build can be started again.

The tables come from the cells of the recipe and of the intermediate recipes it is built on, narrowed to the selected data sources. The extraction ids are the ones the last build used - created or reused - so they are empty before the first build. Nothing here is cached - every call queries the destination once.

ready is true when every listed table exists. A recipe whose cells reference no extraction tables answers with ready: false and an empty sources list. A table exists once the first account's rows land in it, so ready does not mean that every account has delivered, and it can be true while the recipe is still Extracting Data; the recipe state is the readiness signal.