self-join followed by a projection with duplicated names results in panic

[jimexist]

Describe the bug
A clear and concise description of what the bug is.

this is most likely on how we deal with self-joins

To Reproduce
Steps to reproduce the behavior:

SELECT
  t1.c9, t2.c9
FROM test t1
INNER JOIN test t2
ON t1.c9 = t2.c9;

thread 'main' panicked at 'index out of bounds: the len is 1 but the index is 1', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/arrow-4.4.0/src/datatypes/schema.rs:165:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expected behavior
A clear and concise description of what you expected to happen.

this would work in Postgres

Additional context
Add any other context about the problem here.

[houqp]

This should be fixed by #605

>  CREATE EXTERNAL TABLE test(c9 int)
STORED AS CSV
LOCATION '/tmp/foo.csv';
0 rows in set. Query took 0.000 seconds.
> SELECT
  t1.c9, t2.c9
FROM test t1
INNER JOIN test t2
ON t1.c9 = t2.c9;
+----+----+
| c9 | c9 |
+----+----+
| 4  | 4  |
| 3  | 3  |
| 1  | 1  |
| 2  | 2  |
+----+----+
4 rows in set. Query took 0.021 seconds.