We observed that `DdlChanges` in `MySqlDatabaseSchema` is reset with every new `parseDdl` call during snapshotting and streaming. However, during schema history recovery, the DDL parser doesn't do the same.

This leads to unnecessary memory being accumulated until a DDL is consumed by the task from the streaming phase.

Fix –
We need to clear the `DdlChanges` inside the the parser itself, so that all implementations benefit from it and memory is not clogged.