flashback: support to flashback to tso syntax (#48493)

[BornChanger]

This is an automated cherry-pick of #48493

What problem does this PR solve?

Issue Number: close #48372

Problem Summary:

What changed and how does it work?

This PR provide the flashback cluster to tso support.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

This feature provides the new syntax of `flashback` of `flashback cluster to tso xxx_int`. An example is `flashback cluster to tso 445494955052105728`.

[tiprow]

Hi @BornChanger. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[BornChanger]

/retest

[tiprow]

@BornChanger: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-7.5@f27e4e0). Click here to learn what that means.
The diff coverage is 76.9230%.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #51125   +/-   ##
================================================
  Coverage               ?   72.2668%           
================================================
  Files                  ?       1403           
  Lines                  ?     409575           
  Branches               ?          0           
================================================
  Hits                   ?     295987           
  Misses                 ?      93858           
  Partials               ?      19730           

Flag	Coverage Δ
unit	72.2668% <76.9230%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9913% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.3162% <0.0000%> (?)

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-02-18 10:56:07.956384384 +0000 UTC m=+181856.704007496: ☑️ agreed by Leavrth.
• 2024-02-19 02:29:13.858663024 +0000 UTC m=+237842.606286120: ☑️ agreed by YuJuncen.

[bb7133]

LGTM

[easonn7]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, D3Hunter, easonn7, Leavrth, YuJuncen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [D3Hunter,Leavrth,YuJuncen,bb7133]
• pkg/parser/OWNERS [D3Hunter,bb7133,easonn7]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.