[fix](Nereids) join order is not right after sql parsing (#28721)

[morrySnow]

pick from master
PR #28721
commit e51e94f

for sql

t1, t2 join t3

we should generate plan like:

t1 join (t2 join t3)

but we generate:

(t1 join t2) join t3

to follow legancy planner.

Proposed changes

Issue Number: close #xxx

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[morrySnow]

run buildall

[doris-robot]

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.39 seconds
stream load tsv: 563 seconds loaded 74807831229 Bytes, about 126 MB/s
stream load json: 20 seconds loaded 2358488459 Bytes, about 112 MB/s
stream load orc: 65 seconds loaded 1101869774 Bytes, about 16 MB/s
stream load parquet: 33 seconds loaded 861443392 Bytes, about 24 MB/s
insert into select: 29.7 seconds inserted 10000000 Rows, about 336K ops/s
storage size: 17162126340 Bytes