AWAN-100: Remove manual Room database migrations and enable destructive fallback

[ZeiadT]

What & Why

As the app is in initial development, Room database version has been reset to 1, and manual migrations have been removed in favor of \allbackToDestructiveMigration(dropAllTables = true). This ensures seamless database table recreation during rapid schema iterations without identity-hash mismatch crashes.

Key Changes

• Reset Room database version to 1 in \AwanDatabase.kt.
• Removed all \MIGRATION_*\ objects and unused Room migration imports from \AwanDatabase.kt.
• Cleaned \DatabaseModule.kt\ by removing .addMigrations(...)\ while keeping .fallbackToDestructiveMigration(dropAllTables = true).
• Deleted obsolete migration unit & instrumented test files.
• Deleted obsolete schema export files (2.json through 6.json) and regenerated version 1 schema (\1.json).

Related

AWAN-100

Testing

• :core:database:kspDebugKotlin\ (Generated version 1 schema)
• :core:database:testDebugUnitTest\ (Passed 0 errors)
• :app:assembleDebug\ (Passed 0 errors)

[mSaayeh]

Please ignore migrations for now, as the app is still in development. We can reinstall the app and lower the number of migrations because it's constantly increasing.

[mSaayeh]

Great work, just a stale document attached that needs to be removed

[mSaayeh]

Great Job!