VReplication: disable use of session_track_gtids

[shlomi-noach]

Description

An alternative approach to #16421, addressing #16420.
It's really a completely different take: this PR disables the use of tracked session GTIDs, essentially undoing some of the work in #11061. VReplication table streamer and row streamer will only ever use the tried-and-true flush tables with read lock to capture a transactionally consistent GTID.

There are multiple reasons here. First, the discrepancy of behavior we have right now between different flavors of MySQL, and across different CI jobs. This makes debugging and reproducibility more difficult to handle, and we've struggled with this for a while.
Next, and what actually kicks this work, is we're seeing a bug, and incorrect value for the tracked GTID, under certain workloads and with specific table structures. We began investigation into this. Out of precaution, we prefer to disable it at this time.

Related Issue(s)

#16420

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.

[deepthi]

Looks fine. I expect there might be some test failures which have to be fixed.

[shlomi-noach]

We expect no test failures in this PR's CI jobs, as they all use vanilla MySQL, and so the behavior is effectively unchanged.

[shlomi-noach]

OK, we choose to continue with this PR, over #16421 which I will now close.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.66%. Comparing base (c9c0aa5) to head (8d42a01).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #16424   +/-   ##
=======================================
  Coverage   68.66%   68.66%           
=======================================
  Files        1548     1548           
  Lines      199071   199063    -8     
=======================================
+ Hits       136683   136696   +13     
+ Misses      62388    62367   -21     

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