lightning: tolerate tikv node address changes during importing (#32876)

[ti-srebot]

cherry-pick #32876 to release-5.4
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/33107

After apply modifications, you can push your change to this PR via:

git push [email protected]:ti-srebot/tidb.git pr/33107:release-5.4-9c4f94dd7001

---

What problem does this PR solve?

Issue Number: close #32875

Problem Summary:

Lightning cannot restore successfully while tikv store address changes.

What is changed and how it works?

1. Implement custom gRPC resolver.
2. Increase the max retry times for write and ingest.

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

lightning: tolerate tikv node address changes during importing 

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

[ti-srebot]

/run-all-tests

[ti-srebot]

@gozssky you're already a collaborator in bot's repo.

[sleepymole]

/close

[ti-chi-bot]

@gozssky: Closed this PR.

In response to this:

/close

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.