filter (ticdc): simplify filter interface and apply event filter rule in ddlPuller (#9549)

[ti-chi-bot]

This is an manual cherry-pick of #9549 and #9577

What problem does this PR solve?

Issue Number: close #9531 #9571

What is changed and how it works?

1. The ShouldIgnoreDDLEvent() method has been removed from the filter interface and its functionality has been integrated into the ShouldDiscardDDL() method. This makes the filter interface more readable and consistent.
2. DDLs can be skipped in the ddlPuller by setting eventFilter or IgnoreTxnStartTs in the filter configuration. This allows users to control which DDLs are processed, which can be useful for performance or debugging purposes. It is also helpful when we need to skip DDLs that cannot be handled by TiCDC.
3. Add a detailed error message to inform the user how to skip an DDL when it can not be handle by TiCDC.
   

Check List

Tests

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

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]

PR needs rebase.

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

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

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

[asddongmen]

/test all