[FEATURE] Scope OpenSearch-only PPL functions to OpenSearch adapter & data sources

Is your feature request related to a problem?

OpenSearch-only PPL functions (e.g., match, query_string, etc.) are currently hard-coded in the ANTLR grammar and registered in the PPL-Calcite function registry as if they were universally available. This lets queries that use full-text search functions pass parsing and semantic checks even when no OpenSearch data source is referenced, only to fail at runtime.

What solution would you like?

Scope OpenSearch-only functions so they are only valid when the OpenSearch adapter is plugged in and the query actually involves an OpenSearch data source. In all other cases, function resolution should fail during analysis with a clear syntax/analysis error message.

What alternatives have you considered?

• Maintain a list for functions from PPLBuiltinOperatos must not be registered for non-OpenSearch engine.
• Add a validator to detect OpenSearch-only functions and guard runtime by failing early.

Do you have any additional context?

• Spark function catalog: https://spark.apache.org/docs/3.5.4/api/java/org/apache/spark/sql/connector/catalog/FunctionCatalog.html
• Calcite adapter function: https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/schema/Schema.java#L130

Start by tracing the ANTLR grammar and the PPL-Calcite function registry, then compare the proposed FunctionCatalog and Calcite adapter approaches. Verify how the active data source is identified and how function resolution reports errors. Done means OpenSearch-only functions resolve only for OpenSearch queries and fail clearly during analysis otherwise.