puller(ticdc): reduce the CPU cost when remove the changefeed

[3AceShowHand]

What problem does this PR solve?

Issue Number: close #xxx

What is changed and how it works?

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

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from 3aceshowhand, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}

[asddongmen]

This log is really helpful in debugging.

[3AceShowHand]

I am doubting shall we really print so much logs, it's extreamly hard to open the log file

[asddongmen]

Please do not change it until a full test is conducted to verify that it will not impact performance.

[3AceShowHand]

This PR won't be merged, after all other signification problems get fixed. When merging this PR, we should also care about the performance of the log puller won't regressed.

[ti-chi-bot]

@3AceShowHand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-check	9fab0bc	link	true	/test pull-check
pull-unit-test	9fab0bc	link	true	/test pull-unit-test
pull-cdc-mysql-integration-light	9fab0bc	link	true	/test pull-cdc-mysql-integration-light
pull-cdc-storage-integration-light	9fab0bc	link	true	/test pull-cdc-storage-integration-light

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