fix: warn streaming requests are not retryable

[kuhe]

Current behavior when retrying a streaming payload:

• client hangs, the stream has been read for the initial request and cannot be read again for the retry

In this PR:

• a warning is logged: "An error was encountered in a non-retryable streaming request."
• the error is thrown regardless of its retryable status

---

How to reproduce streaming retry:

import { S3 } from "@aws-sdk/client-s3";
import { NodeHttpHandler } from "@smithy/node-http-handler";
import { Readable } from "stream";

function streamToString(stream) {
  const chunks = [];
  return new Promise((resolve, reject) => {
    stream.on("data", (chunk) => chunks.push(Buffer.from(chunk)));
    stream.on("error", (err) => reject(err));
    stream.on("end", () => resolve(Buffer.concat(chunks).toString("utf8")));
  });
}

const s3 = new S3({
  region: "us-west-2",
  requestHandler: new (class {
    constructor() {
      this.call = 0;
      this.handler = new NodeHttpHandler({});
    }

    async handle(req) {
      if (this.call++ === 0) {
        const body = await streamToString(req.body);
        console.log("mock error has read the stream body", body);
        throw {
          $metadata: {
            httpStatusCode: 500,
          },
        };
      }
      return this.handler.handle(req);
    }
  })(),
});

const Bucket = "....";

await s3.putObject({
  Bucket,
  Key: "retry-stream",
  Body: Readable.from("abcd"),
  ContentLength: 4,
});

This PR prevents retries for streaming payloads because we cannot restore the stream.
A warning is also logged prior to the error.

[kuhe]

fixes aws/aws-sdk-js-v3#5479

[vvo]

@kuhe We're getting these warnings for unrelated errors, for example when trying to pass an UploadId that doesn't exist in an UploadPartCommand. I wonder if always sending the stream warning on any error is what we really want here?