make receive_timeout configurable

[michaelwang13]

This exposes the httpclient receive_timeout property to be configurable by the end-user. This can be a useful setting to adjust when users hit errors like:

[warn]: #0 failed to flush the buffer. retry_times=0 next_retry_time=2024-09-26 18:35:54 +0000 chunk="REDACTED" error_class=HTTPClient::ReceiveTimeoutError error="execution expired"
2024-09-26T18:35:52.924897251Z 2024-09-26 18:35:52.924711734 +0000 fluent.warn: {"retry_times":0,"next_retry_time":"2024-09-26 18:35:54 +0000","chunk":"REDACTED","error":"#<HTTPClient::ReceiveTimeoutError: execution expired>","message":"failed to flush the buffer. retry_times=0 next_retry_time=2024-09-26 18:35:54 +0000 chunk=\"REDACTED\" error_class=HTTPClient::ReceiveTimeoutError error=\"execution expired\""}

[michaelwang13]

@sumo-drosiek is it possible to get some eyes on this + release? the fluentd plugin is sending a significant number of duplicate/tripled up logs, and we need to be able to configure this setting.

[echlebek]

Hi Michael, Dominik isn't with Sumo any longer, but I'm happy to take a look at your PR.

[michaelwang13]

Thank you Eric, I appreciate it

[echlebek]

Looks good to me.

[michaelwang13]

Thank you Eric! It looks like I'm unable to cut a new release, can you do that as well so this is usable? @echlebek