planner: include schema name when checking duplicate table aliases

[eurekaka]

What problem does this PR solve?

Issue Number: close #24563
close #24550

Problem Summary:

Incompatible behaviors regarding duplicate table alias check with MySQL.

What is changed and how it works?

What's Changed:

Include schema name when checking duplicate table aliases.

Related changes

N/A

Check List

Tests

• Unit test

Side effects

N/A

Release note

• Fix incompatibility of duplicate table alias check with MySQL

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[eurekaka]

/run-all-tests

[eurekaka]

/run-e2e-test

[eurekaka]

integration-common-test

[eurekaka]

/run-all-tests

[time-and-fate]

Found a bad case:
select * from db1.t as t1, (select * from t) as t1;
This is valid on MySQL 8.0.25 but invalid on this PR.

[ti-chi-bot]

@eurekaka: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[eurekaka]

Well, the behavior difference of MySQL for these 2 queries is pretty confusing.

MySQL [db1]> select * from db1.t as t1, t as t1;
ERROR 1066 (42000): Not unique table/alias: 't1'
MySQL [db1]> select * from db1.t as t1, (select * from t) as t1;
+------+------+
| a    | a    |
+------+------+
|    1 |    1 |
+------+------+
1 row in set (0.00 sec)

[eurekaka]

Close this PR until we find another solution to cover all MySQL behaviors.

[longfeiss]

Well, the behavior difference of MySQL for these 2 queries is pretty confusing.

MySQL [db1]> select * from db1.t as t1, t as t1;
ERROR 1066 (42000): Not unique table/alias: 't1'
MySQL [db1]> select * from db1.t as t1, (select * from t) as t1;
+------+------+
| a    | a    |
+------+------+
|    1 |    1 |
+------+------+
1 row in set (0.00 sec)

tested in MySQL 8.0.27, seems it's valid now

mysql> select version();
+--------------+
| version()    |
+--------------+
| 8.0.27-debug |
+--------------+
1 row in set (0.00 sec)

mysql> select * from db1.t1 as t1, t1 as t1;
Empty set (0.00 sec)