Rename S3 Filesystem config socket-read-timeout to socket-timeout

[danielbelchior]

Description

This PR renames the configuration property s3.socket-read-timeout to
s3.socket-timeout in the S3 filesystem connector. The previous property
name was misleading, as it actually sets the underlying HTTP client's
socketTimeout, which controls both read and write timeouts. The new
property name, s3.socket-timeout, more accurately reflects its behavior
and improves clarity for users configuring S3 timeouts.

Additional context and related issues

The change updates the property name in both the code and documentation to
ensure consistency and avoid confusion. No functional behavior is changed;
the timeout continues to apply to both read and write operations at the
HTTP client level. This update aligns the property name with its actual
semantics and helps prevent misconfiguration by users.

Release notes

## Delta Lake connector
* Rename `s3.socket-read-timeout` config property to `s3.socket-timeout` to make it more clear that the timeout applies equally to socket read and write operations. ({issue}`26263`)

## Hudi connector
* Rename `s3.socket-read-timeout` config property to `s3.socket-timeout` to make it more clear that the timeout applies equally to socket read and write operations. ({issue}`26263`)

## Hive connector
* Rename `s3.socket-read-timeout` config property to `s3.socket-timeout` to make it more clear that the timeout applies equally to socket read and write operations. ({issue}`26263`)

## Iceberg connector
* Rename `s3.socket-read-timeout` config property to `s3.socket-timeout` to make it more clear that the timeout applies equally to socket read and write operations. ({issue}`26263`)

Closes: #26088

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[wendigo]

We don't do breaking changes like that. We use @LegacyConfig to redirect previous config property to a new one.

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[danielbelchior]

Hi @ebyhr can you please help me with the CLA approval? I have 5 other PR waiting for this approval.

[pettyjamesm]

Hi @ebyhr can you please help me with the CLA approval? I have 5 other PR waiting for this approval.

cc: @martint - CLA approval request

[ebyhr]

/test-with-secrets sha=a513434853670d70af73ed913ea732839253af57

[github-actions]

The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/16456523843

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[martint]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[pettyjamesm]

Approved, thanks @danielbelchior!