Enable Calcite by default and implicit fallback the unsupported commands

[LantaoJin]

Description

1. Set the default value of plugins.calcite.enabled to true
2. Implicit to fallback to v2 for any failure with CalciteUnsupportException:
   https://github.com/opensearch-project/sql/blob/d6394dff93a2b8ae458137bfec8674dbfc0c6821/docs/user/ppl/limitations/limitations.rst#unsupported-functionalities-in-calcite-engine

Related Issues

Resolves #4314

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[LantaoJin]

RestHandlerClientYamlTestSuiteIT > test {yaml=issues/3102/Prevent push down limit if the offset reach max_result_window} FAILED
    java.lang.AssertionError: Failure at [issues/3102:26]: expected [2xx] status code but api [ppl] returned [500 Internal Server Error] [{
      "error": {
        "reason": "There was internal problem at backend",
        "details": "java.sql.SQLException: Error while preparing plan [LogicalSystemLimit(fetch=[10000], type=[QUERY_SIZE_LIMIT])\n  LogicalProject(id=[$0])\n    LogicalSort(offset=[1], fetch=[1])\n      CalciteLogicalIndexScan(table=[[OpenSearch, test]])\n]",
        "type": "RuntimeException"
      },
      "status": 500
    }]

This CI failure not related. It's a bug triggered by enabling Calcite. #4377 will fix it.

[penghuo]

We should remove combine ppl_cli and ppl_cli_calcite in category.json.

I see. it tracked in seperate PR. #4377

[penghuo]

information_schema is not a command. @vamsimanohar please help confirm. if it not not a command, we should remove it from command list.

[vamsimanohar]

You are right, its not a command. information_schema is a default schema for metadata information. ideally this should be part of describe command.
Lets remove it.
Prometheus is also moving to direct_query_plugin. Shouldn't be a big issue fi we remove it.

[LantaoJin]

cmd/information_schema.rst was removed and its content was moved to ppl/admin/datasources.rst

[dai-chen]

Do we have a list of command or common cases that may trigger fallback? Just a little concern the fallback logic become more complicated (Calcite -> V2 -> legacy).

[LantaoJin]

Do we have a list of command or common cases that may trigger fallback? Just a little concern the fallback logic become more complicated (Calcite -> V2 -> legacy).

Unsupported Functionalities in Calcite Engine

[opensearch-trigger-bot]

The backport to 2.19-dev failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.19-dev 2.19-dev
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.19-dev
# Create a new branch
git switch --create backport/backport-4372-to-2.19-dev
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b9e2761a744b839d0edd86213b13a2cd89322787
# Push it to GitHub
git push --set-upstream origin backport/backport-4372-to-2.19-dev
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.19-dev

Then, create a pull request where the base branch is 2.19-dev and the compare/head branch is backport/backport-4372-to-2.19-dev.