fix: propagate input stream errors through ndJsonStream

[michelTho]

Problem

ndJsonStream uses try/finally to read from the input byte stream. When the input stream errors (e.g. a child process crashes and the ReadableStream controller calls controller.error()), the finally block calls controller.close() on the output message stream, swallowing the error. This causes Connection.#receive() to see a clean EOF instead of the actual error.

As a result, when a process crashes mid-connection:

• Pending sendRequest() calls hang forever (before v0.18.0) or get a generic "ACP connection closed" error (v0.18.0+) instead of the actual crash error
• The signal.reason / closed promise don't carry the original error

Fix

Replace try/finally with try/catch/finally:

• catch: calls controller.error(err) to propagate the error to the message-level ReadableStream, then returns early
• finally: always calls reader.releaseLock()
• controller.close() only runs on the success path (after the try block)

Tests

Added two tests:

• propagates input stream errors through ndJsonStream — verifies the connection closes when the input stream errors immediately
• rejects pending requests when input stream errors via ndJsonStream — verifies in-flight requests are rejected with the original error message

[benbrandt]

Thanks!