[bug] - Ensure detector HTTP clients share the same timeout set at runtime

[ahrav]

Description:

This PR updates the way we handle the user-supplied detectorTimeout so that it also applies to the underlying HTTP clients used by the detectors. Previously, we only set the timeout on the per-detector context, but the actual HTTP client for detectors still used a default timeout value. Now, when the CLI flag detector-timeout is set, we call a function to override the DetectorHttpClientWithLocalAddresses and DetectorHttpClientWithNoLocalAddresses timeouts.
This ensures consistency between the detector code’s context timeout and the HTTP client’s timeout.

I also updated the default timeout to match the previous detectionTimeout value and modified the detectionTimeout variable to use the same DefaultResponseTimeout from our detectors package.

Checklist:

• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?