[Bug] The addition of a new field in MySQL CDC may result in data loss during the data synchronization process

### Search before asking

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

### Paimon version

0.7

### Compute Engine

flink 1.17.2

### Minimal reproduce step

When the paimon table is set to write-only mode, if there are changes to the table structure and the replace method in StoreSinkWriteImpl is executed, the checkpoint obtained from restoreFiles is an empty array. This results in the sequenceNumbers property of the newly created MergeTreeWriter being set to 0.

### What doesn't meet your expectations?

The addition of a new field in MySQL CDC may result in data loss during the data

### Anything else?

_No response_

### Are you willing to submit a PR?

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

Start with StoreSinkWriteImpl, focusing on the replace method and the restoreFiles checkpoint behavior described in the report. Trace how an empty checkpoint affects MergeTreeWriter sequenceNumbers during MySQL CDC schema changes, then verify that adding a field does not lose synchronized data.

Written by the indexing model from the issue text.