Add typed JSON output to store execution

[gonzaloriestra]

WHY are these changes introduced?

Fixes shop/issues-develop#23689.

Scripts need a discoverable result contract for store execute without constraining caller-defined GraphQL fields.

WHAT is this pull request doing?

Adds a shared inferred result type from transport to presenter and validates JSON encoding. Preserves arbitrary response fields, property order, nulls, omissions, file contents, and output channels. Stacked on #8566.

Example output

Illustrative sample data. Text excerpts omit terminal decoration and progress. JSON blocks show the final stdout result; progress and diagnostics go to stderr.

shopify store execute --store shop.myshopify.com --query 'query { shop { name } }'

Text

Operation succeeded.

{
  "shop": {
    "name": "My Shop"
  }
}

JSON (--json)

{
  "shop": {
    "name": "My Shop"
  }
}

With --json --output-file result.json, the query result is written to the file and stdout is empty. Progress and diagnostics remain on stderr.

How to manually test your changes?

shopify store execute --store shop.myshopify.com --query 'query { shop { name } }'
shopify store execute --store shop.myshopify.com --query 'query { shop { name } }' --json
shopify store execute --store shop.myshopify.com --query 'query { shop { name } }' --json --output-file result.json
shopify store execute --json-schema

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• Added a changeset (consolidated in Add typed JSON output for store delete #8585).

[dmerand]

This is a funny one, adding a schema that's "any object". It makes me wonder about this command... but that's a separate concern. Changes LGTM!