Purpose of this pull request

close #8586

Does this PR introduce any user-facing change?

How was this patch tested?

I can simulate and reproduce the scenario where the problem occurred
The testing steps are as follows:
step1: Start the task to synchronize data from MySQL CDC to Redis
step2: After the task synchronization is completed, execute the MySQL command "flush binary logs;" to create a new binlog file
step3: Wait to receive the binlog heartbeat event and the next checkpoint events
step4: Pause Task
step5: Execute the MySQL command “purge binary logs before 'xxx“ to delete the previous binlog file
step6: Restore Task
Error will occur before modification
After modification, the task can be restored normally

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config
• Update the release-note.