regenerate migration files

[Ezi-code]

Description (summary)

This PR regenerates and replaces the project's migration files to eliminate duplicate migration numbers (for example, multiple 0009_... files) and prevent future merge conflicts caused by merged/split migration history. Rather than attempting to reconcile several conflicting migration files, I created new, linearized migration files with unique names so that the repository has a clean, deterministic migration sequence.

Motivation and context

• The repo contained multiple migrations with the same numeric prefix (e.g., 0009_..., 0009_...) and some merged/squashed migration artifacts. This causes confusing history and increases the risk of migration conflicts and accidental schema drift when different branches are merged.
• Regenerating migrations ensures a single, consistent migration chain, reducing friction for future changes and CI runs.
• This is a low-risk, preventative maintenance change intended to make migrations easier to apply and maintain across developer machines and deploys.

[miraclousharshita]

@Ezi-code Thanks for your work. There is no need for removing migrations right now. It keep tracks of all the changes done in db during migration. This can be done once the app is at a stable state or deployed for production usecase

[Ezi-code]

@Ezi-code Thanks for your work. There is no need for removing migrations right now. It keep tracks of all the changes done in db during migration. This can be done once the app is at a stable state or deployed for production usecase

We had a discussion about it on Slack before, so I think it's fine.