fix(cli): support start machine output

[ametel01]

Summary

Adds machine-output handling for supabase start in the legacy TypeScript shell. For --output json and --output-format json|stream-json, the command now captures Go start stdout, waits for a successful start, then emits the same status payload as supabase status --output json.

Legacy --output env|toml|yaml follows the same start-then-status path, while text output remains delegated directly to Go. The side-effect docs now describe the new output behavior.

Issue

Addresses the supabase start --output json workflow requested in #4675 and discussed in #4675 (comment).

Output

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:67d4cea3af

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:d6ea0488de

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[jgoux]

Thanks for your contribution! 🙏