owner(ticdc): Add backoff mechanism into changefeed restart logic (#4262)

[ti-chi-bot]

This is an automated cherry-pick of #4262

What problem does this PR solve?

Issue Number: close #3329 close #3987

What is changed and how it works?

Before this optimization:
When errors occurred in a changefeed, a simple backoff is leveraged to restart a changefeed:
If there are three errors which occurred in two minutes, the changefeed stays in "error" state and won't be restarted imediately.

After this optimization:
We utilize an exponential backoff mechanism in the changefeed restart logic. The mechanism is elaborated as follows:

1. When we need to restart a changefeed in "error" state, the restart interval is varying from an InitialInterval to a MaxInterval. And if the duration since backoff start exceed the MaxElapsedTime, the changefeed will be switched to "failed" state and will not be restarted until it is manually resumed.
2. If the changefeed was running normally in a period of time and it encounters error at present, we can reset the backoff and let the restart interval vary from the InitialInterval.

Check List

Tests

• Unit test
• Integration test

Release note

Add exponential backoff mechanism for restarting a changefeed.

[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-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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.