Add typed JSON output to app logs sources

[gonzaloriestra]

WHY are these changes introduced?

Related to https://github.com/shop/issues-develop/issues/23670.

app logs sources has no machine-readable output or discoverable result schema.

WHAT is this pull request doing?

Add --json with typed source records containing the filter string, extension identity, configuration, paths and capabilities already available locally. Keep namespace sections in text output and preserve invalid-app exit behavior.

Expose the schema in help and refresh generated documentation. Each record's source is the value accepted by app logs --source.

Output example: text vs JSON

Illustrative app with one function extension. JSON is an excerpt; additional metadata fields are omitted.

Text — shopify app logs sources --path /path/to/app

EXTENSIONS
extensions.cart-discount

JSON — shopify app logs sources --path /path/to/app --json

[
  {
    "source": "extensions.cart-discount",
    "namespace": "extensions",
    "handle": "cart-discount",
    "name": "Cart discount",
    "type": "function",
    "directory": "/path/to/app/extensions/cart-discount",
    "configurationPath": "/path/to/app/extensions/cart-discount/shopify.extension.toml",
    "entrySourceFilePath": "/path/to/app/extensions/cart-discount/src/index.js",
    "outputPath": "/path/to/app/extensions/cart-discount/dist/index.wasm"
  }
]

The source value can be passed directly to shopify app logs --source extensions.cart-discount.

How to manually test your changes?

pnpm shopify app logs sources --path /path/to/app
pnpm shopify app logs sources --path /path/to/app --json
pnpm shopify app logs sources --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