Migration method seems not to be idempotent #2
Description
Looking at the method that you have for migrating changes, it doesn't seem to be idempotent.
It seems to assume that it is always called from a previous version to a newer version.
Also, it seems that each migrator doesn't get information about the version it is migrated from, unless that is part of the loro_doc itself.
It is expected that each migrator ignores versions that are more up-to-date than what it is designed to migrate?
You only have version one, so it is very hard to try to guess what the workflow will be, so a comment about that would be awesome.
Regards