[cdc] optimize database sync table filter logic

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.

### Paimon version

master

### Compute Engine

flink

### Minimal reproduce step

none

### What doesn't meet your expectations?

In the current database_sync logic, if the including_tables or excluding_tables parameters are set, a series of parsing and conversion logic will still be performed on the tables that need to be filtered. We should filter them as soon as we can get the tableName to avoid some meaningless parsing and conversion operations.

### Anything else?

_No response_

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Locate the database_sync implementation and trace how including_tables and excluding_tables are applied after tableName becomes available. Confirm where parsing and conversion occur, then verify that filtered tables bypass those operations and run the relevant database-sync tests or checks.

Written by the indexing model from the issue text.