feat(storage) Parity: AWS SDK S3 accelerate via useAccelerateEndpoint pluginOptions.

[harsh62]

Originally opened by @jcjimenez in #2631 ... Taking up the work from there to finish it.

Issues

#2591
#1542

Description of changes

This change makes it possible to leverage the existing AWS SDK S3 configuration in the same way that it is done for Javascript/React. #featureparity

Check points: (check or cross out if not relevant)

• Added new tests to cover change, if needed
• Build succeeds with all target using Swift Package Manager
• All unit tests pass
• All integration tests pass
• Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
• Documentation update for the change if required
• PR title conforms to conventional commit style
• If breaking change, documentation/changelog update with migration instructions

Testing Procedure Followed

1. Ensure the S3 bucket used by Amplify has Transfer Acceleration disabled.
   
2. Ensure all integration tests pass.
3. Enable transfer acceleration locally by updating the tests under AWSS3StoragePluginAccelerateIntegrationTests setting useAccelerateEndpoint to true.
4. Run the integration tests. They should all fail.
5. Enable Transfer Acceleration using the AWS Console.
   
6. Ensure the integration tests now pass.
   
7. Disable transfer acceleration locally by updating the tests under AWSS3StoragePluginAccelerateIntegrationTests setting useAccelerateEndpoint to false.
8. Ensure the integration tests pass, even though the client is no longer using the accelerate feature and the S3 bucket still has it enabled.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[harsh62]

Passing integration tests: https://github.com/aws-amplify/amplify-swift/actions/runs/5547710256/jobs/10134540934