Add redirection awareness for RENAME table operation

[findinpath]

Description

Add redirection awareness for the ALTER TABLE xxx RENAME TO yyy statement.

The implementation follows the specification from #11202 (comment)

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

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

This implementation affects the core query engine.

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

In the context of working in an environment where Hive/Iceberg/Delta tables are mixed, allow the user to do a table rename by deriving the destination catalog and schema from the source table name.

When having the table redirection enabled in the hive connector (via hive.iceberg-catalog-name=iceberg in hive.properties) and a table iceberg.default.iceberg_table_name within the iceberg connector, any of the following statements is considered valid:

     ALTER TABLE hive.default.iceberg_table_name to iceberg_table_name_new;
     ALTER TABLE hive.default.iceberg_table_name to default.iceberg_table_name_new;
     ALTER TABLE hive.default.iceberg_table_name to iceberg.default.iceberg_table_name_new;

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) 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:

# Main
* Add redirection awareness for RENAME table operation

[findepi]

define a newTableName variable

[findepi]

why target -> source ?

[findinpath]

This was a mistake. Thank you for raising this point.

[findepi]

do we have test coverage for this?

[findinpath]

We have a few tests:

• io.trino.security.TestAccessControl#testNonQueryAccessControl -> is using a rather naive io.trino.testing.TestingAccessControlManager behind the scenes (and no systemAccessControls)
• io.trino.testing.BaseConnectorTest#testRenameTable

However I haven't found a test interacting with a fine grained system access control implementation like https://trino.io/docs/current/security/file-system-access-control.html

[findepi]

Did any test fail when you had target here?

[findinpath]

No. There were no failures as far as I can recall.
https://github.com/trinodb/trino/actions/runs/1922889046

[findepi]

Can you please add a test? Orthogonal to this PR

[findepi]

actually…. there should be two tests: we should have an access control test for rename; and we should have an access control test for rename with redirects; we should verify which table AC is asked about

[findinpath]

Created #11488 as a scaffolding for dealing with access control tests for redirections. I'll be adding support for RENAME TABLE there once it reaches master.