api(ticdc): Check min service gc safepoint when resume changefeed

[sdojjy]

What problem does this PR solve?

Issue Number: close #10463

What is changed and how it works?

currently, when the user resumes a failed changefeed, CDC does not do any GC safe point checking even if the data is already GCed. After this PR, when the user resumes a changefeed, CDC checks weather the current checkpoint ts is smaller than the min service gc safepoint or not. If smaller, ticdc open API will return an ErrStartTsBeforeGC error.

Check List

Tests

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

Questions

Will it cause performance regression or break compatibility?

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

Release note

 `None`.

[codecov]

Codecov Report

Merging #10546 (da6426e) into master (5d5ec56) will increase coverage by 0.0097%.
Report is 12 commits behind head on master.
The diff coverage is 62.5000%.

Additional details and impacted files

Components	Coverage Δ
cdc	61.7975% <62.5000%> (+0.0089%)	⬆️
dm	51.2376% <ø> (+0.0121%)	⬆️
engine	63.3999% <ø> (+0.0070%)	⬆️

Flag	Coverage Δ
unit	57.4939% <62.5000%> (+0.0097%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

@@               Coverage Diff                @@
##             master     #10546        +/-   ##
================================================
+ Coverage   57.4842%   57.4939%   +0.0097%     
================================================
  Files           849        848         -1     
  Lines        126099     126095         -4     
================================================
+ Hits          72487      72497        +10     
+ Misses        48195      48140        -55     
- Partials       5417       5458        +41     

[ti-chi-bot]

@flowbehappy: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asddongmen, CharlesCheung96, flowbehappy

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 [CharlesCheung96,asddongmen]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-26 03:04:39.616216733 +0000 UTC m=+1102721.180514425: ☑️ agreed by asddongmen.
• 2024-01-26 05:09:53.787593616 +0000 UTC m=+1110235.351891322: ☑️ agreed by CharlesCheung96.

[ti-chi-bot]

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

[ti-chi-bot]

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