planner: support cross shard DELETE with LIMIT/ORDER BY

[systay]

Description

This PR add support for Delete with Limit optionally having Order By for sharded keyspaces.

Related Issue(s)

• Vitess does not support DML DELETE JOIN syntax #6854

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

Deployment Notes

[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: 313 lines in your changes are missing coverage. Please review.

Comparison is base (9af8692) 47.33% compared to head (3ea0b81) 47.36%.
Report is 13 commits behind head on main.

Files	Patch %	Lines
go/vt/vtgate/planbuilder/operators/delete.go	0.00%	32 Missing ⚠️
.../vtgate/planbuilder/operators/delete_with_input.go	0.00%	31 Missing ⚠️
go/vt/vtgate/engine/delete_with_input.go	53.70%	23 Missing and 2 partials ⚠️
go/vt/vttablet/onlineddl/executor.go	4.00%	24 Missing ⚠️
.../vt/vtgate/planbuilder/operators/query_planning.go	0.00%	17 Missing ⚠️
go/vt/vtenv/cached_size.go	0.00%	14 Missing ⚠️
go/vt/vtgate/planbuilder/operators/phases.go	0.00%	14 Missing ⚠️
go/vt/vtctl/workflow/server.go	79.66%	10 Missing and 2 partials ⚠️
go/vt/sqlparser/cached_size.go	0.00%	10 Missing ⚠️
go/vt/vttablet/tabletserver/tabletenv/env.go	0.00%	10 Missing ⚠️
... and 50 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14959      +/-   ##
==========================================
+ Coverage   47.33%   47.36%   +0.03%     
==========================================
  Files        1142     1144       +2     
  Lines      239009   239066      +57     
==========================================
+ Hits       113125   113239     +114     
+ Misses     117289   117242      -47     
+ Partials     8595     8585      -10     

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

[GuptaManan100]

LGTM!