cdc: fix old value config glitch when changefeeds with different settings connect to one region (#9515)

[ti-srebot]

cherry-pick #9515 to release-4.0
You can switch your code base to this Pull Request by using git-extras:

# In tikv repo:
git pr https://github.com/tikv/tikv/pull/9565

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tikv.git pr/9565:release-4.0-927e36f952f8

---

What problem does this PR solve?

Problem Summary:
When two TiCDC changefeeds connect to the same region, but one changefeed requires old value but the other doesn't, the one that doesn't need old value still receives old value.

What is changed and how it works?

What's Changed: Now we record the old value setting in each Downstream and filters the old value appropriately before sinking the events.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Release note

• Fix old value config glitch when changefeeds with different settings connect to one region

[ti-srebot]

/run-all-tests

[ti-srebot]

@liuzix please accept the invitation then you can push to the cherry-pick pull requests.
https://github.com/ti-srebot/tikv/invitations

[liuzix]

/run-all-tests

[liuzix]

/cc @leoppro

[zier-one]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 5kbpers
• leoppro

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[liuzix]

/run-all-tests

[NingLin-P]

/merge

[ti-chi-bot]

@NingLin-P: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

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]

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

Commit hash: 6f7fecf

[NingLin-P]

/merge

[ti-chi-bot]

@NingLin-P: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

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.