S3 crt client HeadObject call freezes.

### Describe the bug

We are running a service where we read data from s3 parallelly(multithreading), one day we saw all the threads are still running as head response from S3 freezes with no response ever returned(All new threads are also in struck state leading to accumulation of lot of threads). However this issue is fixed once we restarted the service.

Unfortunately, we have not been able to reproduce this issue since. While investigating, we found a similar issue in the AWS SDK for JavaScript [here](https://github.com/aws/aws-sdk-js/issues/295). Could you please confirm if this is indeed a similar issue? The suggested solution in that case was to configure an HTTP timeout.

We considered doing the same, but we discovered that the S3 CRT client does not honor timeout configurations, as mentioned in [this issue](https://github.com/aws/aws-sdk-cpp/issues/2594). Could you provide information on when the AWS S3 CRT client will support timeout configurations? This support is crucial to ensure that we do not encounter S3 API call freezes in the future.

### Expected Behavior

HeadObject call shouldnot freeze

### Current Behavior

HeadObject call freezes.

### Reproduction Steps

Unable to reproduce, but its better to configure HTTP timeout

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### AWS CPP SDK version used

1.11.269

### Compiler and Version used

gcc (GCC) 4.8.5

### Operating System and version

CentOS Linux and version 7

Start by reviewing the S3 CRT client's HeadObject path and how it handles HTTP timeout configuration, using the linked AWS SDK for JavaScript and AWS SDK for C++ timeout issues as context. Done means establishing whether a configured timeout is honored and preventing the call from remaining frozen indefinitely, although the report provides no reproduction or named test.

Vom Indexierungsmodell aus dem Issue-Text verfasst.