[Bug] Using paimon_fink_action to synchronize MySQL tables to Paimon issue

### Search before asking

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

### Paimon version

1.2

### Compute Engine

flink1.18

### Minimal reproduce step

mysql_sync_table
--warehouse
--database
--table
--primary_keys id
--mysql_conf hostname=
--mysql_conf port=
--mysql_conf username=
--mysql_conf password=
--mysql_conf database-name=
--mysql_conf table-name='cdctest_([0-9]+)?'
--table_conf changelog-producer=input
--table_conf bucket=-1

### What doesn't meet your expectations?

version
flink1.18
paimon1.2
cdc3.2

mysql_sync_table
--warehouse
--database
--table
--primary_keys id
--mysql_conf hostname=
--mysql_conf port=
--mysql_conf username=
--mysql_conf password=
--mysql_conf database-name=
--mysql_conf table-name='cdctest_([0-9]+)?'
--table_conf changelog-producer=input
--table_conf bucket=-1

When starting this task, tables starting with cdctest_ were indeed recognized and synchronized. However, if a table starting with cdctest_ is added in MySQL without restarting the task, why doesn't it automatically recognize and synchronize the table

### Anything else?

_No response_

### Are you willing to submit a PR?

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

Start at the mysql_sync_table entry point and reproduce the issue using the listed Paimon 1.2, Flink 1.18, and CDC 3.2 versions. Add a matching cdctest_ table in MySQL while the task is running and investigate table discovery; done means the new table is recognized and synchronized without restarting the task.

Written by the indexing model from the issue text.