owner(ticdc): fix the issue of resolvedTs may stuck when no table is synchronized

[CharlesCheung96]

What problem does this PR solve?

Issue Number: ref #8963

What is changed and how it works?

In PR #8964, newRsolvedTs can not advanced if no tables are replicated, so we should advance newResolvedTs to globalBarrierTs in such case.

Check List

Tests

• Unit test
• Integration test

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

None`.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• asddongmen
• nongfushanquan

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[CharlesCheung96]

/test all

[CharlesCheung96]

/test all

[CharlesCheung96]

/retest

[CharlesCheung96]

/test all

[CharlesCheung96]

/test all

[nongfushanquan]

The processor to handle the resolved ts and checkpoint ts in tick() is too complex now. we should make it simply.

[CharlesCheung96]

/merge

[ti-chi-bot]

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

Commit hash: 5cadf0c

[ti-chi-bot]

@CharlesCheung96: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

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.

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]

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

[ti-chi-bot]

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