[Maintenance] Merge Calcite feature branch to main

[LantaoJin]

Our target is releasing the Calcite execution engine of PPL on OpenSearch in v3.0.0.
On this first release, it will include:

• 1. Leverage Apache Calcite query planner as the PPL query optimizer
• 2. Leverage Apache Calcite linq4j enumerator as the PPL query execution backend (in coordinator node)
• 3. Support new PPL commands including Join/Lookup/Subsearch on OpenSearch.
• 4. Support pushdown Filter, Project, and partial Aggregation operator to OpenSearch cluster.
• 5. Support almost existed functions and core data types.
• 6. Automatically fallback to V2 engine when a query is unsupported in new engine.

Check its parent issue for details and status of all open issues.

This issue is for addressing the current gaps before merging to main branch:

1. Resolve all blocker issues (will list in comment).
2. Resolve all conflicts with main branch. The merging action MUST use rebase only.
3. Improve necessary code coverage, disabled for now.
4. Migrate all existing ITs to new engine.
5. Create issues for all unsupported usages/cases.
6. Identify those bug fixes which made in dev branch and backport them to 2.x. (for example [BUG] Issues in PPL grammar #3391 (comment))
7. Provide docs for new functionality (may open a new issue after release code freeze)

[LantaoJin]

@penghuo @dai-chen , let me know if anything I miss

[LantaoJin]

v3.0.0-beta blockers(not tech blocker):

commands:
#3358
#3347
#3407

expressions:
#3354
#3333
#3420
#3432
#3439
#3452

functions:
#3398
#3399
#3400
#3401
#3417

types:
Would #3322 and its children be treated as blockers?

[penghuo]

6. Automatically fallback to V2 engine when a query is unsupported in new engine.

I would like to know which types of commands or functions trigger the fallback. We have observed that the current V2 engine fallback approach results in a poor user experience. My suggestion is to create clear documentation that outlines the limitations for each command and function will fallback.

[penghuo]

Also consider benchmark V2 and V3 engine and publish results.