fix: handle streamed response failure

[bigujun]

Node process crashes with Uncaught Error when a readable stream is destroyed with an error when using express.

Reproduce steps:

@Get('/stream-with-error')
async getStream() {
  return new Readable({
    read() {
      this.destroy(new Error());
    }
  });
}

One workaround is to watch for the error event and manually close the underlying connection.

@Get('/stream-with-error')
async getStream(@Request() req: express.Request) {
  const readable = new Readable({
    read() {
      this.destroy(new Error());
    }
  });
  // listening to error prevents `Uncaught Error`;
  readable.on('error', () => {  
    // close the connection, so the response will not hang indefinitely on the client side;
    req.destroy();
  });
  return readable;
}

The problem is that readable.pipe(...) does not properly handle errors, so replacing it with pipeline solves the problem, since pipeline will properly clean up.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you written unit tests?
• Have you written unit tests that cover the negative cases (i.e.: if bad data is submitted, does the library respond properly)?
• This PR is associated with an existing issue?

Closing issues

closes #1664

Test plan

Included an express integration test that fails when the patch is not applied.
Test case simulates a readable that will be destroyed with an error and expects the connection to be aborted.
Without the fix applied, the process will throw an Uncaught Error and test will fail.
With the fix applied, the connection will be properly aborted and test will pass.

[github-actions]

Hello there bigujun 👋

Thank you and congrats 🎉 for opening your first PR on this project.✨

We will review the following PR soon! 👀