Use separate XML writer for S3 operations

[davidh44]

Motivation and Context

Currently, when calling DeleteObjects with an object key that contains characters that need to be escaped in XML, and is encoded, the decoded key is deleted instead.

e.g., sending DeleteObjectsRequest specifying the key <Key>objectId</Key> deletes the object with the key <Key>objectId</Key>

This is because the XmlWriter performs unescaping.

Modifications

Created a separate S3XmlWriter which does not perform unescaping, which will be used exclusively for S3 operations.

Testing

Added integ tests

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarcloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

15 New issues
0 Security Hotspots
86.9% Coverage on New Code
1.0% Duplication on New Code

See analysis details on SonarCloud