Add support to redirect table reads from Hive to Iceberg

[findepi]

Hive Connector redirects Iceberg table access to the configured
Iceberg catalog.

This change adds implementation of HiveTableRedirectionsProvider,
plugging in Hive->Iceberg redirects and leveraging existing framework.

This is based on work from several authors. In particular, this is based
on #8340 with conflicts resolved, and retrofit to current APIs in Hive connector.

As tests show, not all the statements support redirects properly and
this needs to be followed up upon.

[findepi]

per @ssheikin's #8340 (comment), added @MiguelWeezardo as co-author.

[losipiuk]

Is there a reason why we do not care about properties which are set to null in events?

[findepi]

I am not aware of any consumer of these events. This must be some extension point for someone.
The only usage i found looks like a dummy consumer, at least this is what the commit message says.

trino/plugin/trino-hive/src/main/java/io/trino/plugin/hive/HiveEventClient.java

Lines 31 to 38 in cea5842

	log.debug("File created: query: %s, schema: %s, table: %s, partition: '%s', format: %s, size: %s, path: %s",
	writeCompletedEvent.getQueryId(),
	writeCompletedEvent.getSchemaName(),
	writeCompletedEvent.getTableName(),
	writeCompletedEvent.getPartitionName(),
	writeCompletedEvent.getStorageFormat(),
	writeCompletedEvent.getBytes(),
	writeCompletedEvent.getPath());

Including null values could be a breaking change to downstream even consumers (e.g. if the [Immutable]Map.copyOf(event.getSessionProperties()). Converting values to Optional would be a breaking change to. In the absence of more information, i deemed that omitting null values is the least breaking of all options.

[losipiuk]

This probably does not matter here but I heard many times in the past that we should refrain from using singlenode envs as they provide worse test coverage than multinode ones.

[findepi]

Thanks for reminding me. We have 27 or something singlenode environments. And yes, here it doesn't matter, as tested functionality is really coordinator-only. Let me keep it as is.

[losipiuk]

can you create a github issue which lists missing functionalities?
And tag relevant TODOs with an issue

[findepi]

I don't think it's necessary in this case. #8340 is going to fix this problems (once #8340 (comment) is resolved).

[hashhar]

Do we want to test SHOW STATS redirection too?

What about a non-default hive.timestamp-precision? Redirects will return different results.
Same for the use_column_name configs in tables which have different schema across partitions.

[findepi]

What about a non-default hive.timestamp-precision? Redirects will return different results.

hive.timestamp-precision doesn't matter, since there is no Hive table. Hive doesn't know the table schema, so it doesn't know whether there are any timestamps.

Same for the use_column_name configs in tables which have different schema across partitions.

same

[findepi]

Do we want to test SHOW STATS redirection too?

added

Also, split the test class into two (#10173 (comment)).

[aierate]

Do I have to use like
USE a-catalog.myschema;
SELECT * FROM mytable;
or
SELECT * FROM a-catalog.myschema.mytable;
?
Instead of using SELECT * FROM myschema.mytable without using a-catalog or USE a-catalog?