fix(lib-storage): add validation for partCount and contentLength for multipart upload

[smilkuri]

Issue

Internal JS-6196

Description

• Adds validation to check total number of UploadPart requests the SDK has sent matches the expected number of parts.
• Adds validation to check the content length of each UploadPart request matches the expected part size.

Testing

Locally
yarn test and yarn test:e2e are successful

host % yarn test

 RUN  v3.2.4 /aws-sdk-js-v3/lib/lib-storage

 ✓ src/chunks/getChunkUint8Array.spec.ts (6 tests) 7ms
 ✓ src/chunks/getDataReadableStream.spec.ts (4 tests) 168ms
 ✓ src/chunks/getDataReadable.spec.ts (3 tests) 167ms
 ✓ src/index.spec.ts (1 test) 2ms
 ✓ src/Upload.spec.ts (34 tests) 22888ms
   ✓ Upload > should add tags to the object if tags have been added multi-part  22807ms

 Test Files  5 passed (5)
      Tests  48 passed (48)
   Start at  16:15:06
   Duration  23.90s (transform 861ms, setup 0ms, collect 2.42s, tests 23.23s, environment 1ms, prepare 584ms)

Checklist

• [n/a] If the PR is a feature, add integration tests (*.integ.spec.ts).
• [n/a] If you wrote E2E tests, are they resilient to concurrent I/O?
• [n/a] If adding new public functions, did you add the @public tag and enable doc generation on the package?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kuhe]

what falsy values does byteLength return? What if it's zero?

[smilkuri]

It can return zero for empty parts, may be for scenarios like empty file?

[kuhe]

if byteLength can return undefined, then the expression should be byteLength(dataPart.data);

zero byte length should not be converted to undefined.