fix: incorrect set preserve_partitioning in SortExec

[haohuaijin]

Which issue does this PR close?

related to #8374

Rationale for this change

In #8374, we find ProjectionPushdown will incorrectly push projection down and rewrite order by column,
before

select t1.* from t1 join t2 on t1.a = t2.a order by t1.a, t2.b;

after

select t1.* from t1 join t2 on t1.a = t2.a order by t1.a, t1.b;

the sort column change from t1.a, t2.b to t1.a, t1.b.

However, even if we find the root case, we can still not explain why setting the order by column incorrectly results in an empty output. After doing some tests, I discovered that we did not set the preserve_partitioning in SortExec. As a result, SortExec only run one partition(instead of all partition), leading to an empty output.

What changes are included in this PR?

make SortExec's preserve_patitioning consistent before and after projection_pushdown

Are these changes tested?

yes, add .slt test

Are there any user-facing changes?

[waynexia]

Looks good to me 👍

[alamb]

Thank you @haohuaijin and @waynexia