Add ambiguous check when generate projection plan

[ygf11]

Describe the bug
When the two table both has c0, then the following sql will work:

❯ explain select c0 from test0, test1;
+---------------+-----------------------------------------------------------------------------------------------------+
| plan_type     | plan                                                                                                |
+---------------+-----------------------------------------------------------------------------------------------------+
| logical_plan  | Projection: test0.c0                                                                                |
|               |   CrossJoin:                                                                                        |
|               |     TableScan: test0 projection=[c0]                                                                |
|               |     TableScan: test1 projection=[c0]                                                                |

The projection part of this sql is not clear, datafusion should throw an error.

To Reproduce
Create two table test0 and test1, which both contain c0.
Run sql explain select c0 from test0, test1;

Expected behavior

Additional context

[mingmwang]

What's the behavior in other systems? Like SparkSQL and PostgreSQL ?

[ygf11]

Like #4197 and #4196, it will also report an error in PostgreSQL:

psql -d "$POSTGRES_DB" -h "$POSTGRES_HOST" -p "$POSTGRES_PORT" -U "$POSTGRES_USER" -c "select c0 from test0, test1"
ERROR:  column reference "c0" is ambiguous
LINE 1: select c0 from test0, test1
               ^