fix: Register the s3:// scheme when an S3 connection is configured

[sweb]

Description

Right now, you need to tell Trino explicitly to write to s3a:// when issuing a CTAS against the Hive Metastore (e.g. for Iceberg tables) - by also registering the s3:// scheme, this is no longer required and can stay with the s3:// scheme.

Important to note: If we decide that this is a good direction, we should also add the s3:// scheme to the Spark configuration so that this works cross products without additional configuration.

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)
• Release note snippet added

Reviewer

• Code contains useful comments
• Code contains useful logging statements
• (Integration-)Test cases added
• Documentation added or updated. Follows the style guide.
• Changelog updated

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added

Release Notes

Fixed

Previously, users would have to explicitly tell e.g. Trino to use s3a:// schemes when issuing CTAS against the Hive Metastore. With this release, the s3:// scheme is registered as well, allowing users to keep the default location scheme.

[razvan]

nice

[lfrancke]

@sweb
Please add a release note snippet in the form "Previously, this went wrong. With this release, this was fixed in the following way."

[sweb]

@sweb Please add a release note snippet in the form "Previously, this went wrong. With this release, this was fixed in the following way."

Done