Set http_continue_timeout to nil for s3 client

What does this MR do and why?

Recently noticed there are errors/messages not being sent to AWS S3 audit event streaming destinations, there are no new objects being created despite audit events being created.

Set http_continue_timeout to nil for s3 client to resolve this.

Changelog: fixed

References

• #577190 (closed)
• https://gitlab.slack.com/archives/CN7C8029H/p1760418194481259

Screenshots or screen recordings

Example object:

{"id":16807,"author_id":1,"entity_id":1000000,"entity_type":"Group","details":{"event_name":"group_share_with_group_link_created","author_name":"Administrator","author_class":"User","target_id":24,"target_type":"Group","target_details":"Gitlab Org","custom_message":"Invited Gitlab Org to the group GitLab Duo","ip_address":"172.16.123.1","entity_path":"gitlab-duo"},"ip_address":"172.16.123.1","author_name":"Administrator","entity_path":"gitlab-duo","target_details":"Gitlab Org","created_at":"2025-10-14T18:00:08.677Z","target_type":"Group","target_id":24,"event_type":"group_share_with_group_link_created"}

How to set up and validate locally

• Setup AWS s3 streaming destination either in group or instance settings
• Test with the feature flag audit_events_fix_streaming_filters as it will set to default true (edge case testing)
• Objects should be created in s3.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.