VReplication: Unify VReplication and VTGate VStream Retry Logic

[mattlord]

Description

In VTGate VStreams, we've been returning errors to the client in various cases where a retry is likely to succeed. The most egregious example is the query interrupted MySQL error (see issue) that we expect to get from each tablet during the copy phase — when multiple copy phase cycles are required — every vreplication_copy_phase_duration. We expect that for large tables in Vitess v19.0 and later after the work done in #13840 .

This PR addresses this case and a variety of others by leveraging some of the same retry logic that we use for vreplication streams.

Related Issue(s)

• Fixes: Bug Report: VTGate VStream API Does not Properly Handle Multiple Copy Phase Cycles #17778

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.96%. Comparing base (000fbbe) to head (fd73c53).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17783      +/-   ##
==========================================
+ Coverage   67.95%   67.96%   +0.01%     
==========================================
  Files        1586     1586              
  Lines      255208   255218      +10     
==========================================
+ Hits       173423   173468      +45     
+ Misses      81785    81750      -35     

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