fix(goods): handle stream read errors in responseToReadable

[swaraj792725]

Fixes #1443

Description

In responseToReadable, the rs._read implementation calls await reader.read() without a try/catch block. When stream reading fails or is aborted (e.g., network disconnect or abort signal), the rejected promise is unhandled by Node's stream internals, resulting in an unhandled promise rejection process crash.

This PR wraps await reader.read() in a try/catch block and calls rs.destroy(err) when an error occurs, properly destroying the readable stream and allowing error handlers to catch it gracefully.

Testing

• Added unit test in test/goods.test.ts verifying stream error handling in responseToReadable.
• Also updated build scripts and test runners to use fileURLToPath from node:url for robust cross-platform path resolution when folder names contain spaces.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[swaraj792725]

I have signed the Google CLA.

[swaraj792725]

@googlebot I signed it!