Update Iceberg version to 1.8.0

[ebyhr]

Description

The following PR broke our integration with older REST catalogs:

• Core: Add missing REST endpoint definitions apache/iceberg#11756
• Core: Use HEAD request to check if namespace exists apache/iceberg#11761
• Core: Use HEAD request to check if view exists apache/iceberg#11760
• REST: Use HEAD request to check table existence apache/iceberg#10999

AWS SDK bump broke our integration with S3-compatible storages (pre-2025 Minio, Vast, Dell EC etc):

• S3: Add LegacyMd5Plugin to S3 client builder apache/iceberg#12264

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

[wendigo]

this will break iceberg in storage like ECS. Can we force iceberg not to use storng integrity checks?

[ebyhr]

I reported the issue at Iceberg Slack today: https://apache-iceberg.slack.com/archives/C03LG1D563F/p1739434861646329?thread_ts=1739417985.509649&cid=C03LG1D563F

[ebyhr]

I'm fixing product test failures.

[wendigo]

@ebyhr do we plan to merge it? What's the scope of the strong integrity checks issue?

[ebyhr]

@wendigo I think we should wait for 1.8.1. There are 2 issues - REST catalog compatibility apache/iceberg#12294 and S3 strong integrity checks. The scope of S3 issue is limited because most IO happens with our file system module. However, the scope of REST catalog issue is unclear because it depends on each REST catalog's implementation. I believe this update breaks integration not just with Polaris and Unity, but with most REST catalogs.

[ebyhr]

Anther PR with 1.8.1 RC #25094

[ebyhr]

Closing as we will update to 1.8.1 instead #25094.