Improve errant GTID detection in ERS to handle more cases.

[GuptaManan100]

Description

This PR adds the code changes for reworking the errant GTID detection in ERS. As proposed in #16724 (comment), we now also use the reparent journal length as an extra data point for GTID detection. All the different cases listed in #16274 have been added as unit tests in this PR, and the expectations of the algorithm have been verified.

Since, ReadReparentJournalInfo is a new RPC, there can be customers that upgrade Vitess multiple versions at a time (we are adding the new RPC in v21, but it is not available in releases prior to that). In this case, the vttablets won't have the RPC implemented. Since we don't want ERS to stop working in this situation, we have to keep the legacy errant GTID code around for this scenario. So, if reading the reparent journal information fails on any tablet, then we revert to using that legacy errant GTID detection code.

Related Issue(s)

• Fixes Bug Report: vtorc ERS incorrectly flags replica as having errant GTIDs #16724

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 86.70213% with 25 lines in your changes missing coverage. Please review.

Project coverage is 69.37%. Comparing base (538dd4c) to head (f3fead6).
Report is 159 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vttablet/tabletmanager/rpc_replication.go	0.00%	11 Missing ⚠️
go/vt/vtctl/reparentutil/emergency_reparenter.go	95.00%	5 Missing ⚠️
go/mysql/replication/replication_status.go	93.10%	2 Missing ⚠️
go/vt/mysqlctl/reparent.go	0.00%	2 Missing ⚠️
go/vt/vtcombo/tablet_map.go	0.00%	2 Missing ⚠️
go/vt/vttablet/faketmclient/fake_client.go	0.00%	2 Missing ⚠️
go/vt/vttablet/grpctmclient/client.go	88.88%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16926      +/-   ##
==========================================
+ Coverage   68.98%   69.37%   +0.38%     
==========================================
  Files        1562     1571       +9     
  Lines      200690   204339    +3649     
==========================================
+ Hits       138449   141750    +3301     
- Misses      62241    62589     +348     

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