VALUES statement AST and parsing

[harshit-gangal]

Description

This PR cherry picks the commit from #16703.

• SQL parsing support for VALUES statements

mysql> VALUES ROW(1,2), ROW(2,3);
+----------+----------+
| column_0 | column_1 |
+----------+----------+
|        1 |        2 |
|        2 |        3 |
+----------+----------+
2 rows in set (0.00 sec)

Related Issue(s)

• Proposal to Optimize Join Operations with Chunking Using VALUES Statement #16508

Checklist

• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

Attention: Patch coverage is 46.74330% with 139 lines in your changes missing coverage. Please review.

Project coverage is 67.68%. Comparing base (ec29bdb) to head (7bd4c1b).
Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/sqlparser/ast.go	0.00%	59 Missing ⚠️
go/vt/sqlparser/ast_funcs.go	41.79%	39 Missing ⚠️
go/vt/sqlparser/ast_format.go	0.00%	15 Missing ⚠️
go/vt/vtgate/planbuilder/operators/SQL_builder.go	62.50%	6 Missing ⚠️
go/vt/vtgate/semantics/table_collector.go	62.50%	6 Missing ⚠️
go/vt/vtgate/semantics/analyzer.go	60.00%	4 Missing ⚠️
go/vt/vtgate/semantics/early_rewriter.go	60.00%	4 Missing ⚠️
go/vt/vtexplain/vtexplain_vttablet.go	50.00%	2 Missing ⚠️
go/vt/vtgate/planbuilder/operators/expressions.go	80.00%	1 Missing ⚠️
.../vt/vtgate/planbuilder/operators/query_planning.go	87.50%	1 Missing ⚠️
... and 2 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17500      +/-   ##
==========================================
- Coverage   67.71%   67.68%   -0.03%     
==========================================
  Files        1584     1584              
  Lines      254519   254637     +118     
==========================================
+ Hits       172338   172362      +24     
- Misses      82181    82275      +94     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[systay]

We shouldn't panic in ast_funcs

[frouioui]

Still looks good to me. I am adding the Do Not Merge label to let either @GuptaManan100 or @harshit-gangal review this before merging the PR.