Adds RPCs to vttablet that vtorc requires

[GuptaManan100]

Description

This PR adds 2 new Tablet manager client RPCs that VTOrc requires -

• ResetReplicationParameters
  • This RPC stops the replication (if running) and resets the replication parameters like source host, port, etc from the server. It does not however clear out the executed gtid set or retrieved gtid set. In MySQL equivalent this function does STOP REPLICA; RESET REPLICA ALL
  • This RPC is supposed to be used in fixPrimaryHasPrimary in VTOrc to reset the replication parameters on the primary tablet
• FullStatus
  • This RPC collects information from the server including replication information, semi-sync settings, server settings among others. The full list of outputs in the full status are -
    • ServerID: Server ID configured :- select @@global.server_id
    • ServerUUID: Server UUID configured/assigned :- select @@global.server_uuid
    • ReplicationStatus: Replication status of the server :- show replica status
    • PrimaryStatus: Binlog position and executed gtid set :- show master status
    • GTIDPurged: purged gtid set :- select @@gtid_purged
    • Version: Server version in the format majorVersion.minorVersion.patchRelease
    • VersionComment: Version comment in the server :- select @@global.version_comment
    • ReadOnly: Whether the server is read only :- show variables like 'read_only'
    • BinLogFormat: format of the binlog of the server :- select @@global.binlog_format
    • BinLogRowImage: the way to store changes to a row in the binlog :- select @@global.binlog_row_image
    • LogBinEnabled: Whether logging in the binlog is enabled :- select @@global.log_bin
    • LogReplicaUpdates: Whether the server will also add the updates acquired via replication to the binlog :- select @@global.log_slave_updates
    • GTIDMode: select @@global.gtid_mode
    • SemiSyncPrimaryEnabled: Whether the primary side semi-sync plugin is enabled :- show global variables like 'rpl_semi_sync_master_enabled'
    • SemiSyncReplicaEnabled: Whether the replica side semi-sync plugin is enabled :- show global variables like 'rpl_semi_sync_slave_enabled'
    • SemiSyncPrimaryStatus: Status of the primary side semi-sync :- show status like 'Rpl_semi_sync_master_status'
    • SemiSyncReplicaStatus: Status of the replica side semi-sync :- show status like 'Rpl_semi_sync_slave_status'
    • SemiSyncPrimaryClients: Number of semi-sync clients of the server :- show status like 'semi_sync_primary_clients'
    • SemiSyncPrimaryTimeout: Amount of time to wait for semi-sync ack before reverting to async replication :- show status like 'rpl_semi_sync_master_timeout
    • SemiSyncWaitForReplicaCount: Number of semi-sync acks required by the server to accept a write :- show status like 'rpl_semi_sync_master_wait_for_slave_count,
  • This RPC is meant to be used in ReadTopologyInstanceBufferable to collect information of the MySQL server without querying it directly

Apart from these 2 RPCs, this PR also augments the ReplicationStatus struct and adds the following new fields to it -

• RelayLogFilePosition - Position of the relay log of the server.
• SourceUser - The source user for the replica.
• SQLDelay - The configured delay that the sql thread is supposed to maintain.
• AutoPosition - Whether GTID auto-positioning is in use
• UsingGTID - If the MariaDB server is using GTIDs for replication
• HasReplicationFilters - If there are any replication filters configured
• SSLAllowed - If the server allows ssl
• ReplicationLagUnknown - Set true if the replication lag is unknown and parsing Seconds_Behind_Primary failed
  An existing field FileRelayLogPosition has been renamed to RelayLogSourceBinLogEquivalentPosition since it is a more apt variable name. The previous variable name would have been too confusing after introducing RelayLogFilePosition
  A test that checks that the rpc changes are backward compatible has also been added.

Related Issue(s)

• RFC: Orchestrator as a native Vitess component #6612

Checklist

• "Backport me!" label has been added if this change should be backported
• Tests were added or are not required
• Documentation was added or is not required

Deployment Notes

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
• If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.

[GuptaManan100]

#10467 uses these introduced RPCs and verifies that they serve their purpose

[deepthi]

These two field names are confusing. It is going to be too easy to make a mistake while making changes in future.

[GuptaManan100]

Yes, renaming the field FileRelayLogPosition to RelayLogSourceBinLogEquivalentPosition

[deepthi]

😆
Guess that's the best we can do to avoid confusion.
I don't know whether binlog is one word - so Binlog vs BinLog
goes to grep vitessio/vitess
OK, we use Binlog almost everywhere except in a few test files. I know this is super-nitpicky, but could you please change it?

[GuptaManan100]

Okay 👍

[deepthi]

One nit, the rest LGTM.
You may merge once that is addressed.