[FEATURE]Replace PPL AST + ANTLR code with dependency

[YANG-DB]

Is your feature request related to a problem?
This Issue is part of the campaign to consolidate PPL into a single grammar location enables simpler and consistent way to evolve the language and moves the responsibility of updating the downstream engine on the engine implementing the spec rather than the grammar & language maintainers..

What solution would you like?
The following tasks:

• add piped-processing-language repo artifacts as a dependency
• remove PPL (SQL) ANTLR
• remove PPL (SQL) Docs
• remove AST (SQL) Docs
• create an additional AST translation layer to add an additional specific engine (OpenSearch) depended Logical step before submitting the Logical plan to be executed - This part need furthermore discussions

Do you have any additional context?

• [RFC] Move PPL Spec & AST into this repository piped-processing-language#23
• https://github.com/opensearch-project/sql/tree/main/ppl/src/main/antlr
• https://github.com/opensearch-project/sql/tree/main/docs
• https://github.com/opensearch-project/sql/tree/main/ppl/src/main/java/org/opensearch/sql/ppl

[normanj-bitquill]

Is this what you envision for the additional AST translation layer?

• In opensearch-project-sql, the AST tree produced by parsing the query is translated to a logical plan (that will be submitted to the OpenSearch server)
• In opensearch-spark, the AST tree produced by parsing the query is translated to a logical plan for Spark. This logical plan is later translated to a physical plan.

[YANG-DB]

Is this what you envision for the additional AST translation layer?

• In opensearch-project-sql, the AST tree produced by parsing the query is translated to a logical plan (that will be submitted to the OpenSearch server)
• In opensearch-spark, the AST tree produced by parsing the query is translated to a logical plan for Spark. This logical plan is later translated to a physical plan.

I was thinking of a similar flow that calcite has for adding the additional dialect layer that knows the specification of each engine and changes the logical plan to be able to be pushed down to the execution layer itself.