sink(cdc): always handle sink failures for cases with sync-point enabled (#10132)

[ti-chi-bot]

This is an automated cherry-pick of #10132

What problem does this PR solve?

Issue Number: close #10091

What is changed and how it works?

In SinkManager, suppose there is a table with checkpointTs=100 and lastWrittenPos=110, and sync-point is also 110.

And then, the sink backend fails, the sink should be re-started at 100.

However, when generating sink tasks, SinkManager finds the table has no more available events after lastWrittenPos=110, and it can't detect the sink backend failure any more.

With the PR this behavior is corrected.

Check List

Tests

• Unit 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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hicqu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hicqu]

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

[hicqu]

/retest

[hicqu]

/retest

[ti-chi-bot]

@ti-chi-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
jenkins-ticdc/verify	6ce7397	link	unknown	/test verify

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[hicqu]

/retest