test(middleware-flexible-checksums): update instructions for MD5 fallback

[siddsriv]

Description

• make middleware ordering relative to flexibleChecksumsMiddleware
• update instructions regarding the DeleteObjects command

Testing

E2E test to confirm removal and addition of relevant headers (uncomment logging in the test file to confirm the headers)

[DeleteObjectsCommand] Headers before MD5 middleware: {
  "content-type": "application/xml",
  "content-length": "145",
  "Expect": "100-continue",
  "x-amz-sdk-checksum-algorithm": "CRC32",
  "x-amz-checksum-crc32": "<signature>"
}
[DeleteObjectsCommand] Removing header: x-amz-sdk-checksum-algorithm
[DeleteObjectsCommand] Removing header: x-amz-checksum-crc32
[DeleteObjectsCommand] Added Content-MD5: <signature>
[DeleteObjectsCommand] Headers after MD5 middleware: {
  "content-type": "application/xml",
  "content-length": "145",
  "Expect": "100-continue",
  "Content-MD5": "<signature>"
}

 ✓ src/middleware-flexible-checksums.e2e.spec.ts (9) 7738ms
 ✓ src/middleware-md5-fallback.e2e.spec.ts (2) 4583ms

 Test Files  2 passed (2)
      Tests  11 passed (11)
   Start at  16:44:45
   Duration  8.44s (transform 259ms, setup 0ms, collect 785ms, tests 12.32s, environment 0ms, prepare 170ms)

Checklist

• If you wrote E2E tests, are they resilient to concurrent I/O?

---

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

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.