Teach optimizer that CoalesceBatchesExec does not destroy output order

[alamb]

Which issue does this PR close?

Closes #4331

Rationale for this change

See #4331

What changes are included in this PR?

Teach optimizer that CoalesceBatchesExec does not destroy output order

Are these changes tested?

Yes

Are there any user-facing changes?

BasicEnforcement will not add unecessary SortExecs

[alamb]

i just need to figure out how to write a test for this PR and it will be ready

[mingmwang]

I think you can construct a UT to test and verify a sorted input stream is still keep sorted after CoalesceBatchesExec

[alamb]

Here is the test (that mimics my usecase in IOx) -- without the changes in this PR this test fails (as there is a SortExec present)

[ursabot]

Benchmark runs are scheduled for baseline = dafd957 and contender = a31b44e. a31b44e 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