Add Iceberg support for ALTER TABLE ... SET PROPERTIES

[alexjo2144]

Description

The two properties which can be set are format and format_version.

Is this change a fix, improvement, new feature, refactoring, or other?

New feature

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Iceberg connector

How would you describe this change to a non-technical end user or system administrator?

Allows updating specific metadata for an Iceberg table. The format_version, and the format of the underlying data files.

Related issues, pull requests, and links

Fixes: #12138

Documentation

( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
(x) Release notes entries required with the following suggested text:

# Iceberg
* Add support for updating the `format` and `format_version` table properties using `ALTER TABLE ... SET PROPERTIES`. This allows for updating tables from v1 of the Iceberg specification to v2.

[findepi]

We should allow changing partitioning, let's have a TODO+issue

[alexjo2144]

#12174

[findinpath]

Add a product test to the class io.trino.tests.product.iceberg.TestIcebergSparkCompatibility for checking the compatibility with Spark on updating table properties.

[alexjo2144]

Add a product test to the class io.trino.tests.product.iceberg.TestIcebergSparkCompatibility for checking the compatibility with Spark on updating table properties.

I was thinking about that, but wasn't sure what exactly was testable from the Spark side. The test I added to TestIcebergV2 is engine-agnostic, using the Iceberg lib directly to check the format version. I don't think there's a SparkSQL query to ask for the format version though.

[alexjo2144]

AC Thanks @findepi @findinpath

Also added documentation

[alexjo2144]

@mosabua mind taking a look at the doc update?

[alexjo2144]

Thanks @findinpath, added those test cases

[findinpath]

SELECT * FROM system.metadata.table_properties where catalog_name = 'iceberg';

Do we / should we have documented somewhere this statement used to retrieve the "updatable" table properties?

[alexjo2144]

Is there a separate doc page for system tables or information_schema? I couldn't find one, but I feel like that's where it should go

[findinpath]

Can we please verify via

assertQuery("SELECT * FROM " + tableName, "SELECT * FROM nation");

that the change of the format_version has no negative outcome for the end user?

[alexjo2144]

Added

And no, I don't think it does

[findinpath]

I was just thinking that it would be good to have it in case of eventual regressions.