fix: gracefully handle invalid json response

[pschiel]

Fixes#7889

Cause:

Aborting requests (e.g., pressing ESC during streaming responses) can result in an empty response body.
The SDK client's JSON parser fails on empty strings with "Unexpected end of JSON input" because there was no error handling.

Fix: add error handling.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Found potential duplicate PRs:

Related PRs (addressing similar/same issue):

1. PR fix: handle empty JSON responses in sdk client #8027 - "fix: handle empty JSON responses in sdk client"

   • Directly addresses empty JSON response handling in the SDK client

2. PR fix(storage): handle empty JSON files gracefully #7888 - "fix(sdk): handle empty JSON response bodies gracefully"

   • Specifically targets empty JSON response bodies gracefully, which matches the fix description

3. PR fix(tui): handle JSON parse error on double-escape abort #7959 - "fix(tui): handle JSON parse error on double-escape abort"

   • Handles JSON parse errors on abort scenarios, related to the ESC abort streaming issue

4. PR fix: add error handling to RPC system to prevent crashes on session abort #7939 - "fix: add error handling to RPC system to prevent crashes on session abort"

   • Related to session abort handling

Why they're related: PR #8104 fixes JSON parsing errors on empty responses from aborted requests. PRs #8027 and #7888 appear to address the exact same issue (empty JSON responses), while #7959 and #7939 address related abort scenarios that can produce invalid responses.

[mrlubos]

@pschiel this will be fixed upstream hey-api/hey-api#3202

[dhruvkej9]

@pschiel this will be fixed upstream hey-api/openapi-ts#3202

When ?? I can't use opencode due to this

[mrlubos]

@dhruvkej9

NOW!!