add tpch sqllogicaltest and remove some duplicated test

[jackwener]

Which issue does this PR close?

Closes #4801.

Rationale for this change

I just want to remove tpch in Unit-Test, because it's duplicated with independent test for TPCH.
But these UT contains some data-test, so I add sqllogicaltest for it.

What changes are included in this PR?

• add tpch sqllogicaltest
• remove some duplicated test.

Are these changes tested?

Are there any user-facing changes?

[jackwener]

Some query result is strange, but run successfully.🤔

[andygrove]

These tests are really to check that subqueries get rewritten as joins rather than being about tpch. The change in the test here just checks for correct results and does not check the details of how the plans are rewritten, so I feel like we are losing some value with this change. However, we also check for expected plans in tpch so maybe this is fine. Would be good to check with @avantgardnerio who originally implemented these tests, or @iajoiner.

[jackwener]

These tests are really to check that subqueries get rewritten as joins rather than being about tpch. The change in the test here just checks for correct results and does not check the details of how the plans are rewritten, so I feel like we are losing some value with this change. However, we also check for expected plans in tpch so maybe this is fine. Would be good to check with @avantgardnerio who originally implemented these tests, or @iajoiner.

After a careful comparison, I find that they are not exactly the same. But they have the same effect, and I'm not sure whether to remove them. Looking forward to listening the opinion of @avantgardnerio and @iajoiner .

[alamb]

Thank you @jackwener

Unless I hear otherwise from anyone I plan to merge this PR in the next day or two

I think it is a significant testing improvement -- given we now have the proper tpch test in https://github.com/apache/arrow-datafusion/blob/169b5228800f991be913b10ffdfd161e2cbc7baf/.github/workflows/rust.yml#L126-L165 I am not even sure the new slt test is adding much value 🤔

[ursabot]

Benchmark runs are scheduled for baseline = 63ae2b9 and contender = e393b28. e393b28 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java