DM's schema tracker doesn't track DDL when we skip some DDLs which will lead to column count unmatch

[lichunzhu]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do? If possible, provide a recipe for reproducing the error.
   Configure binlog-event-filter to filter some DDLs to downstream database.

2. What did you expect to see?
   The binlog-event-filter takes effect and the replication can continue automatically.

3. What did you see instead?
   DM task will pause with error 'column count unmatch'.

Root Cause:

1. DM will not track the DDLs to skip in the schema tracker. Then DM will face count unmatch errors when DM tries to parse DML events from the upstream binlogs.

2. If DM tracks these DDLs in the schema tracker, the generated DMLs will contain skipped columns now. Since the DDL is not executed in the downstream, the DML will also fail in the downstream database.

3. Versions of the cluster

   • DM version (run dmctl -V or dm-worker -V or dm-master -V):
     DM v2.0.3

[okJiang]

from comment pingcap/dm#1975 (comment)

a recent ONCALL requires we also track DDL when it's skipped by handle-error skip. please check and fix it in another PR 😂

and change the PR description, don't close the issue if we didn't correcly handle handle-error skip

wait the second PR for closing.