Multi Target Delete Support

[harshit-gangal]

Description

This PR is an enhancement on earlier PR to add support for multi-target delete.

Example: delete u, m from user u, music m on u.col = m.col
The SQL here deletes rows from two tables using the join condition.

Related Issue(s)

• Closes Wordpress Install error on multi-table delete query #5392
• Multi Table Delete Planner Support #14855

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: Patch coverage is 75.83333% with 29 lines in your changes are missing coverage. Please review.

Project coverage is 65.43%. Comparing base (696fe0e) to head (92046c0).
Report is 59 commits behind head on main.

Files	Patch %	Lines
go/vt/vtgate/planbuilder/operators/dml_planning.go	0.00%	11 Missing ⚠️
.../vt/vtgate/planbuilder/operators/dml_with_input.go	45.00%	11 Missing ⚠️
go/vt/vtgate/planbuilder/operators/delete.go	94.11%	3 Missing ⚠️
go/vt/vtgate/engine/dml_with_input.go	95.23%	1 Missing ⚠️
go/vt/vtgate/planbuilder/delete.go	50.00%	1 Missing ⚠️
go/vt/vtgate/planbuilder/operator_transformers.go	85.71%	1 Missing ⚠️
go/vt/vtgate/planbuilder/operators/update.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15294      +/-   ##
==========================================
- Coverage   67.41%   65.43%   -1.99%     
==========================================
  Files        1560     1561       +1     
  Lines      192752   193632     +880     
==========================================
- Hits       129952   126703    -3249     
- Misses      62800    66929    +4129     

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

[GuptaManan100]

Just a couple of questions, rest lgtm