Rollback on production app about watermelondb

[diegolmello]

Useful workaround:
If data is not corrupted and you can keep the migration, make a new version containing the migration, but removing whatever else you need to remove.
The rollback will require a new version on the stores anyway.
I did it a few years ago and it worked nicely.

[LukasMod]

@diegolmello thanks so much!

I created a rollback version with an older version of the application, but with a new build number. I kept migrations.ts and schema.ts as you said and data was preserved. I think this workaround is good enough for me to handle some edge case in bigger app realeses.