Enable validation pipeline and update all test expected outputs

[yuancu]

Summary

Sub-PR 3/4 for #4892 — splitting the large PR into reviewable pieces targeting feature/validation.

This PR enables the validation pipeline by wiring validate() into QueryService's execute and explain flows, and updates all test expected outputs for the structural and type changes caused by the RelNode ↔ SqlNode round-trip.

What's included

Enablement:

• QueryService — executeWithCalcite() and explainWithCalcite() now call validate(relNode, context) before convertToCalcitePlan()

Test Expected Output Updates (~546 YAML files):

• All explain plan YAML files updated for structural changes (field reordering, projection restructuring, sort index changes) caused by the validation round-trip
• JSON → YAML migration for several explain tests (~78 JSON files removed, replaced by YAML equivalents)

Integration Test Updates:

• CalciteExplainIT, CalcitePPLExplainIT, ExplainIT — assertJsonEquals → assertYamlEqualsIgnoreId
• CalcitePPLBasicIT — testBetweenWithMixedTypes (was error, now works with implicit cast)
• CalciteWhereCommandIT — testInWithMixedType (was error, now works)
• CalciteMultisearchCommandIT / CalcitePPLAppendCommandIT — Schema type changes (string → timestamp for UDT fields)
• CalcitePPLAggregationIT — Exception type change
• CalcitePPLPatternsIT — @Ignore for tests pending [FEATURE] Enhance patterns command output structure for easy type validation #4968
• CalciteBinCommandIT, CalciteNoMvCommandIT — Error message updates
• PPLClickBenchIT — ClickBench plan updates + q41 special handling
• WhereCommandIT — Removed incompatible type test (moved to Calcite-specific test)
• DateTimeFunctionIT — Interval semantics fix
• MatcherUtils — New assertYamlEqualsIgnoreId(List, String) overload

PPL Unit Test Updates:

• Plan structure updates across CalcitePPLAggregationTest, CalcitePPLChartTest, CalcitePPLJoinTest, CalcitePPLStreamstatsTest, CalcitePPLTimechartTest, CalcitePPLTransposeTest, etc.

Reviewer Note

~546 of 583 files are mechanical YAML expected output updates. If CI passes, those are correct. Focus review on the ~37 source/test files.

Dependency

• Requires Add validation infrastructure and type system #5213 (Sub-PR A) and Define operand type checkers for all PPL built-in functions #5214 (Sub-PR B) merged first
• Merge after rebasing onto updated feature/validation

Signed-off-by: Yuanchun Shen yuanchu@amazon.com

[github-actions]

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit ce09da4.

'Diff too large, requires skip by maintainers after manual review'

---

Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.

---

⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.

[github-actions]

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit a494a06.

'Diff too large, requires skip by maintainers after manual review'

---

Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.

---

⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.

[github-actions]

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit c9fc356.

'Diff too large, requires skip by maintainers after manual review'

---

Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.

---

⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.