[request]: Support for customizing client configuration

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue, please leave a comment

**Tell us about your request**

Feature parity with the [Java](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/section-client-configuration.html) and other SDKs which allow for customizing of timeouts on the http transport client.

- [x] Connect Timeout
- [ ] Keep-alive Timeout
- [x] Socket Timeout
- [ ] Total Transfer Timeout
- [x] Retry Strategy

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

It is desirable to use aggressive timeouts or shorter timeouts than hidden defaults for performance and availability, such that you can retry to a different region rather than against the same bucket in the event of a high latency, or high loss connection.

**Are you currently working around this issue?**

Not currently working around this.

**Additional context**

Feature parity on client configuration with other SDKs will allow for migration to rust.

**Attachments**

If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Start by comparing the Rust SDK's current client configuration with the linked Java client-configuration documentation. Identify which connect, keep-alive, socket, total-transfer timeout, and retry-strategy options are in scope, then establish how the requested configuration should behave across regions. Done requires an agreed implementation scope and validation for the supported options.

Written by the indexing model from the issue text.