Test iceberg_tables function with TrinoSnowflakeCatalog

[lukasz-stec]

Description

Implement a simple test for the system.iceberg_tables table function for the TrinoSnowflakeCatalog.
Since TrinoSnowflakeCatalog is read only the original generic test does not work.
Theoretically, we could apply the modifications directly on the snowflake to match the generic test with multiple schemas. However, that seems like an overkill given the implementation just delegates to the listTables method and maps the results.

Additional context and related issues

Release notes

( X) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

[ebyhr]

I think this test is flaky. What happens if a new object is created after listing iceberg.information_schema.tables and before executing iceberg_tables function?

[lukasz-stec]

That was the reason the generic test creates its own schemas but in this case, it is not needed because this test does not create iceberg tables other than potentially during setup.
There is one test that creates a native table but that will not be listed by TrinoSnowflakeCatalog#listTables

[lukasz-stec]

@ebyhr could you run with secrets to actually run this test?

[raunaqmorarka]

/test-with-secrets sha=181dc8c8651fdc68b83c9d3d520ef87e13a3f6b7

[github-actions]

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/12583104964

[ebyhr]

Why do we need to build VALUES query? Can we simplify like below?

        String schemaName = SNOWFLAKE_TEST_SCHEMA.toLowerCase(ENGLISH);
        assertThat(query("SELECT * FROM TABLE(iceberg.system.iceberg_tables(SCHEMA_NAME => '" + schemaName + "'))"))
                .matches("SELECT table_schema, table_name FROM iceberg.information_schema.tables WHERE table_schema = '" + schemaName + "'");

[lukasz-stec]

The QueryAssert is way better, let me try that

[ebyhr]

/test-with-secrets sha=ec70948da143156d369a3a195a9acb7fa134b65f

[github-actions]

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/12648508425

[ebyhr]

Let me close this PR because we revert the function addition in #24719