chore: update fast-xml-parser for 3.6.4 release

[trivikr]

Issue

Internal JS-4435

Description

Update fast-xml-parser to 4.2.5 to release @aws-sdk/[email protected]

Testing

$ client-s3> yarn test:unit
yarn run v1.22.19
$ mocha **/cjs/**/*.spec.js


  endpoint
    ✓ users can override endpoint from client.

  Accesspoint ARN
    ✓ should succeed with access point ARN
    ✓ should sign request with region from ARN is useArnRegion is set
    ✓ should succeed with outposts ARN

  Throw 200 response
    ✓ should throw if CopyObject() return with 200 and empty payload
    ✓ should throw if CopyObject() return with 200 and error preamble
    ✓ should throw if UploadPartCopy() return with 200 and empty payload
    ✓ should throw if UploadPartCopy() return with 200 and error preamble
    ✓ should throw if CompleteMultipartUpload() return with 200 and empty payload
    ✓ should throw if CompleteMultipartUpload() return with 200 and error preamble


  10 passing (38ms)

Done in 0.52s.

$ aws-sdk-js-v3>  yarn test:integration-legacy -t @s3
yarn run v1.22.19
$ cucumber-js --fail-fast -t @s3
..................................................................................................................................................................................................................

24 scenarios (24 passed)
138 steps (138 passed)
0m12.435s

npm tarball for testing: aws-sdk-client-s3-3.6.4.tgz

The tarballs were created by:

• git clean -dfx
• yarn
• yarn lerna run --scope @aws-sdk/client-s3 --include-dependencies build
• yarn lerna exec --scope @aws-sdk/client-s3 npm pack
  • Use npm@<=8, as the files glob doesn't work with npm@9 as per [BUG] npm pack ignores files with * by npm@9 npm/cli#6330

---

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

[stocaaro]

I have confirmed this change updates amplify-js.

[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.