Do not trim leading slashes for copy object and copy part operations

[peterrsongg]

…perations

Description

The .NET SDK trims leading slashes on copy object and copy part operations. This behavior can be turned off by setting DisableTrimmingLeadingSlash to true. This change removes that flag so that the .NET SDK will not trim leading slashes.

Motivation and Context

This is something we can only fix in v4

Testing

dry run in v4 passes.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed

License

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

[muhammad-othman]

nit: I think it is better to remove the slash from the destinationKey instead of adding it to the expectedKey to make this test case different than the second one, or remove the slashes from the next test case.

[peterrsongg]

done

[dscpinheiro]

I think this test could be even better if the data row was:

[DataRow(testKeyWithSlash, "destinationTestKey1.txt", "destinationTestKey1.txt")]

There's already another test case in this class copying testKey somewhere else. The code above will validate the leading slash is handled properly.