Add support for multi table deletes with foreign keys

[GuptaManan100]

Description

This PR makes the changes to support multi-table delete queries along with foreign keys. After the changes in this PR, queries like the following now work -

delete u_tbl1 from u_tbl10 join u_tbl1 on u_tbl10.col = u_tbl1.col

Fuzzer tests for the same have been added and verified everything is working as intended.

Related Issue(s)

• Part of RFC: Foreign Key Support in Vitess #12967

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

Comparison is base (eddb39e) 47.29% compared to head (ef565e6) 47.69%.
Report is 83 commits behind head on main.

Files	Patch %	Lines
go/vt/vtgate/evalengine/cached_size.go	0.00%	41 Missing ⚠️
go/vt/vtgate/planbuilder/operators/delete.go	0.00%	34 Missing ⚠️
.../vtgate/planbuilder/operators/delete_with_input.go	0.00%	31 Missing ⚠️
go/vt/mysqlctl/backupengine.go	7.40%	25 Missing ⚠️
go/vt/vtctl/workflow/traffic_switcher.go	0.00%	25 Missing ⚠️
go/vt/vtgate/engine/delete_with_input.go	53.70%	23 Missing and 2 partials ⚠️
...tgate/planbuilder/operators/aggregation_pushing.go	0.00%	25 Missing ⚠️
go/vt/mysqlctl/builtinbackupengine.go	4.34%	22 Missing ⚠️
go/vt/sqlparser/ast_copy_on_rewrite.go	0.00%	18 Missing ⚠️
go/vt/vtgate/evalengine/expr_tuple_bvar.go	62.50%	14 Missing and 4 partials ⚠️
... and 51 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15081      +/-   ##
==========================================
+ Coverage   47.29%   47.69%   +0.39%     
==========================================
  Files        1137     1155      +18     
  Lines      238684   240266    +1582     
==========================================
+ Hits       112895   114602    +1707     
+ Misses     117168   117058     -110     
+ Partials     8621     8606      -15     

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