executor: support capturing to and replaying from shared storage

[djshow832]

What problem does this PR solve?

Issue Number: close #58861

Problem Summary:
Support writing traffic files to shared storage so that users don't need to copy files from the production cluster to the testing cluster.

What changed and how does it work?

• For capturing, TiDB assigns each TiProxy a sub-directory under the output path, in the form of tiproxy-0, tiproxy-1, ...
• For replaying, TiDB reads the sub-directories under the input path and assigns them to TiProxy instances.
• TiProxy is unaware of the assignment.

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.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from djshow832, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[tiprow]

Hi @djshow832. 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-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 74.24242% with 34 lines in your changes missing coverage. Please review.

Project coverage is 73.6181%. Comparing base (7479804) to head (641faef).
Report is 22 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58862        +/-   ##
================================================
+ Coverage   73.0869%   73.6181%   +0.5311%     
================================================
  Files          1676       1677         +1     
  Lines        463749     467749      +4000     
================================================
+ Hits         338940     344348      +5408     
+ Misses       103956     102468      -1488     
- Partials      20853      20933        +80     

Flag	Coverage Δ
integration	42.9724% <0.0000%> (?)
unit	72.3017% <74.2424%> (+0.0192%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.7359% <ø> (+0.0448%)	⬆️

[djshow832]

/retest

[tiprow]

@djshow832: 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-sigs/prow repository.

[djshow832]

/ok-to-test