chore: fix integration test

[xeniape]

Description

Integration test had errors:

• Caused by: software.amazon.awssdk.services.s3.model.S3Exception: Missing required header for this request: Content-Md5 -> fixed by minio version bump Support AWS S3 new checksums minio/minio#20845 (comment)
• Support for optimize_hash_generation was removed in Trino 470 https://trino.io/docs/current/release/release-470.html
• Fixed AssertionError: Regex pattern did not match. Regex: "Session property 'iceberg.test' does not exist"

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
- [ ] Changes are OpenShift compatible
- [ ] CRD changes approved
- [ ] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Helm chart can be installed and deployed operator works
- [ ] Integration tests passed (for non trivial changes)
- [ ] Changes need to be "offline" compatible

# Reviewer
- [ ] Code contains useful comments
- [ ] Code contains useful logging statements
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added
- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated

[sbernauer]

Code change LGTM, thanks for fixing this!
Looking at

trino-operator/tests/test-definition.yaml

Lines 107 to 109 in b43f8e1

	- name: opa-authorization
	dimensions:
	- trino-latest

, IMHO it would make sense to run the opa-authorization test for all supported Trino versions and not only the latest (think e.g. of LTS users). Especially as this is security-related and we have many Trino users.

However, I know that this requires a bit of jinja templating based on the Trino version.
Not blocking the PR on this though

[xeniape]

Code change LGTM, thanks for fixing this! Looking at

trino-operator/tests/test-definition.yaml

Lines 107 to 109 in b43f8e1

	- name: opa-authorization
	dimensions:
	- trino-latest

, IMHO it would make sense to run the opa-authorization test for all supported Trino versions and not only the latest (think e.g. of LTS users). Especially as this is security-related and we have many Trino users.

However, I know that this requires a bit of jinja templating based on the Trino version. Not blocking the PR on this though

I can look at it in a follow-up (or someone else if interested), thanks 👍

[adwk67]

Also checked on OpenShift :)