fix: correct stdout buffering issues in spawned processes

Adds stdio inheritance to prevent Node.js from dropping console output after 8192 characters due to premature stdout pipe closure before output finishes flushing. Without this, calls like this would truncate after 8192 characters, leading to broken json output:

```
npx --node-options=--inspect -y @modelcontextprotocol/inspector --cli --config .mcp.json --server notion --method tools/list
```

```
# notion mcp server
    "notion": {
      "//": "doppler needs to expose OPENAPI_MCP_HEADERS (and NOTION_TOKEN within it)",
      "command": "bash",
      "args": [
        "-c",
        "doppler run -p 'mcp' -c \"user_${MCP_USER:-$USER}\" -- npx -y @notionhq/notion-mcp-server"
      ]
    },
```

You can see this in their [openapi spec](https://github.com/makenotion/notion-mcp-server/blob/main/scripts/notion-openapi.json), which powers their MCP server.

Author: nsheaps

cli/src/cli.ts

@@ -106,6 +106,10 @@ async function runWebClient(args: Args): Promise<void> {
     await spawnPromise("node", [inspectorClientPath, ...startArgs], {
       signal: abort.signal,
       echoOutput: true,
+      // pipe the stdout through here, prevents issues with buffering and
+      // dropping the end of console.out after 8192 chars due to node
+      // closing the stdout pipe before the output has finished flushing
+      stdio: "inherit",
     });
   } catch (e) {
     if (!cancelled || process.env.DEBUG) throw e;
@@ -151,6 +155,10 @@ async function runCli(args: Args): Promise<void> {
       env: { ...process.env, ...args.envArgs },
       signal: abort.signal,
       echoOutput: true,
+      // pipe the stdout through here, prevents issues with buffering and
+      // dropping the end of console.out after 8192 chars due to node
+      // closing the stdout pipe before the output has finished flushing
+      stdio: "inherit",
     });
   } catch (e) {
     if (!cancelled || process.env.DEBUG) {