Add parsing support for ANY/SOME/ALL comparison modifiers.

[arthurschreiber]

Description

This PR introduces support for the ANY and ALL operators in subqueries within the Vitess SQL parser.
For the time being, it's only supported when the query can be merged into a single query that is passed down to MySQL.

Example Usage

SELECT *
FROM employees
WHERE salary > ANY (SELECT salary FROM interns);

SELECT *
FROM employees
WHERE salary > ALL (SELECT salary FROM interns);

Related Issue(s)

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• 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.

[arthurschreiber]

Note: This currently allows using the ANY/SOME/ALL modifiers in combination with the null safe comparison operator (<=>) which is not actually allowed by MySQL.

Output provided by @systay:

mysql> select * from foo where b <=> any (select id from t1);
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '<=> any (select id from t1)' at line 1

This should probably be fixed so our parser matches MySQL's parser more closely.

[codecov]

Codecov Report

Attention: Patch coverage is 77.77778% with 4 lines in your changes missing coverage. Please review.

Project coverage is 68.26%. Comparing base (87ecae7) to head (c5ed057).
Report is 2 commits behind head on main.

Files	Patch %	Lines
go/vt/sqlparser/ast_format.go	66.66%	2 Missing ⚠️
go/vt/vtgate/semantics/analyzer.go	75.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16080      +/-   ##
==========================================
+ Coverage   68.19%   68.26%   +0.06%     
==========================================
  Files        1541     1544       +3     
  Lines      197369   197737     +368     
==========================================
+ Hits       134605   134994     +389     
+ Misses      62764    62743      -21     

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

[GuptaManan100]

I have pushed a fix now for the parser conflicts. I've also made the parser fail for queries that have null safe equality with a column modifier! 💕

[GuptaManan100]

LGTM