fix: In multi-level nested subquery, the field relationships of different tables are wrong

[KKould]

What problem does this PR solve?

ref:

• https://github.com/duckdb/duckdb/blob/main/src/planner/binder/tableref/bind_subqueryref.cpp#L7C1-L31C2

Issue link: #169

explain SELECT b FROM t1 WHERE a in (SELECT a FROM t2 where a in (select a from t1));

+-------------------------------------------------------------------------+
| PLAN                                                                    |
+=========================================================================+
| Projection [t1.b] [Project]                                             |
|   LeftSemi Join On t1.a = (t2.a) as (_temp_table_1_.a) [HashJoin]       |
|     Scan t1 -> [a, b] [SeqScan]                                         |
|     Projection [(t2.a) as (_temp_table_1_.a)] [Project]                 |
|       Projection [t2.a] [Project]                                       |
|         LeftSemi Join On t2.a = (t1.a) as (_temp_table_0_.a) [HashJoin] |
|           Scan t2 -> [a] [SeqScan]                                      |
|           Projection [(t1.a) as (_temp_table_0_.a)] [Project]           |
|             Projection [t1.a] [Project]                                 |
|               Scan t1 -> [a] [SeqScan]                                  |
+-------------------------------------------------------------------------+

What is changed and how it works?

Code changes

• Has Rust code change
• Has CI related scripts change

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Note for reviewer