Run plan tests in end to end configuration

[systay]

Description

We’ve frequently encountered planner tests that assert faulty query plans, which would crash if executed directly on MySQL. This PR enhances testing by running these queries, with data, against both MySQL and Vitess, ensuring the results are consistent and correct across both systems.

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]

Nice! This will be a great help in making sure we catch planner issues earlier. 👍

[codecov]

Codecov Report

Attention: Patch coverage is 15.51724% with 98 lines in your changes missing coverage. Please review.

Project coverage is 67.45%. Comparing base (ab7b516) to head (c476d58).
Report is 15 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtgate/engine/plan_description.go	0.00%	92 Missing ⚠️
go/vt/vtgate/vindexes/lookup_cost.go	75.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17117      +/-   ##
==========================================
+ Coverage   67.41%   67.45%   +0.03%     
==========================================
  Files        1576     1578       +2     
  Lines      253417   253541     +124     
==========================================
+ Hits       170846   171028     +182     
+ Misses      82571    82513      -58     

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

[systay]

Thank you @harshit-gangal for picking this up and running with it. It looks great now. I can't accept my own PR, but if I could, I would! 👍

[frouioui]

This is good! Any plan on running more plan tests in E2E?

[harshit-gangal]

This is good! Any plan on running more plan tests in E2E?

This should be done as and when the planner is modified.