Align how timeout setting act on S3 and Azure storage

[phoebusm]

https://github.com/aws/aws-sdk-cpp/blob/64f29bce3a497111c2ab272bcb50ac5d568d5573/src/aws-cpp-sdk-core/source/http/crt/CRTHttpClient.cpp#L468 https://github.com/Azure/azure-sdk-for-cpp/blob/17c3cb50f158005497860525a07e23718e7d8878/sdk/core/azure-core/inc/azure/core/context.hpp#L240

Currently, 200000ms is the universal setting of request_timeout for both S3 ans Azure storage. However, the setting on S3 monitors at a more finer level - at each http request. For Azure, the setting monitors at a more granular level - at the entire API call. It needs to be addressed, as it has created unwanted timeout in #1026. Or it needs to be dropped per https://github.com/man-group/ArcticDB/pull/1487#pullrequestreview-1993794122, to rely on curl timeout completely.