Fix S3GC is broken on AWS

[JaySon-Huang]

What problem does this PR solve?

Issue Number: close #7158

Problem Summary: As issue described. And find CopyObject request time out after fixing that problem.

What is changed and how it works?

• Add MetadataDirective::REPLACE to CopyObject
• Delete subkeys of DMFile in parallel to shorten the GC time
• Changed storage.s3.request_timeout_ms default to 7 seconds, storage.s3.max_connections default to 4096
  • S3 GC rewriting CheckpointDataFile cause about 3~4 seconds
• Add some metrics and loggings about S3 GC time comsume
• Add a settings remote_gc_method to allow using scan instead of lifecycle for running GC on S3

Check List

Tests

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

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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Lloyd-Pottiger
• lidezhu

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-all-tests

[lidezhu]

LGTM

[JaySon-Huang]

/merge

[ti-chi-bot]

@JaySon-Huang: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: eab7ff1

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.0: #7172.