[FLINK-39114][filesystem] Support configurable timeout in native-s3-fs

[Samrat002]

What is the purpose of the change

This pull request makes hardcoded timeout values in the Native S3 FileSystem configurable via Flink configuration options. Previously, timeouts for HTTP connections, socket reads, connection idle time, filesystem close, and client close were hardcoded constants. From an operational standpoint, these should be tunable to accommodate different network environments and deployment scenarios.

Brief change log

• Added 4 new ConfigOption fields:
  1. s3.connection.timeout, s3.socket.timeout
  2. s3.connection.max-idle-time
  3. s3.close.timeout
  4. s3.client.close.timeout
• Default values match the previous hardcoded values (no behavior change without explicit configuration)

Verifying this change

• Added testCustomTimeoutConfiguration in NativeS3FileSystemFactoryTest that creates a filesystem with all custom timeout values and verifies successful creation

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: yes

Documentation

• Does this pull request introduce a new feature? yes
• If yes, how is the feature documented? JavaDocs

[flinkbot]

CI report:

• abdf2dc Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[spuru9]

LGTM +1

[Izeren]

Thank you for the change @Samrat002, I suggest we use Duration type to follow standard Flink approach for time based configurations