feat: Add support timeouts in milliseconds for HTTP client

[nikolicaleksa]

Adds support for having timeout and connection timeout in milliseconds for HTTP client

[cleptric]

Why do you see the need to reduce the timeout below 1s?

[nikolicaleksa]

Why do you see the need to reduce the timeout below 1s?

TLDR: We would like to reduce it to 250ms, risking dropping some exceptions but not blocking PHP-FPM workers for a second or more.

Detailed:
We encountered the following situation

• We were getting a lot of requests to the application where some of them were failing and logging the exception to Sentry
• We are using Sentry Relay, but for some reason it was unavailable
• Because of that, our PHP-FPM workers were blocked for the full duration of a configured timeout which resulted in a lot of workers being blocked and therefor we were returning 504 errors

We now solved the first issue about many requests by adding the rate limiter, however as an additional precaution we also want to reduce the Sentry timeout to 250ms because we would rather drop some exceptions than block workers for at least a second in case of unavailability.

[mfb]

So is CURLOPT_TIMEOUT only an integer? Meaning CURLOPT_TIMEOUT_MS would also be needed to configure 1.5 seconds?