refactor: Remove PhysicalPlan trait and use ExecutionPlan directly

[evenyag]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

• Remove unnecessary traits and wrapper types from the query crate #3884
• Partitioned scan for RegionEngine #3886

What's changed and what's your intention?

While implementing the RegionScanner trait mentioned in #3886, I need to adapt the scanner to an ExecutionPlan of the datafusion. I found that we could remove the PhysicalPlan trait from the codebase to reduce some indirections.

This PR removes the PhysicalPlan trait and related adapters: DfPhysicalPlanAdapter and PhysicalPlanAdapter.

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR does not require documentation updates.

[codecov]

Codecov Report

Attention: Patch coverage is 77.96610% with 13 lines in your changes are missing coverage. Please review.

Project coverage is 85.68%. Comparing base (fa6c371) to head (6b1c2b3).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3894      +/-   ##
==========================================
- Coverage   85.97%   85.68%   -0.30%     
==========================================
  Files         961      960       -1     
  Lines      164471   164247     -224     
==========================================
- Hits       141409   140738     -671     
- Misses      23062    23509     +447     

[fengjiachun]

LGTM

[tisonkun]

LGTM.

Does this patch close the two issues linked above?

[evenyag]

LGTM.

Does this patch close the two issues linked above?

No. It is a part of them.

[waynexia]

Draft this to avoid an incoming potential conflict

[evenyag]

Did we fix this test in the main branch?

--- TRY 4 STDERR:        tests-integration::main integration_http_file_test::test_prom_http_api ---
thread 'integration_http_file_test::test_prom_http_api' panicked at tests-integration/tests/http.rs:555:5:
assertion `left == right` failed
  left: Labels(["memory", "cpu"])
 right: Labels(["cpu", "memory"])