fix(expo-sqlite): make journal optional in useMigrations migration config

[sleitor]

Fixes #5214

Problem

useMigrations() requires a journal property in the second argument, but the journal field is never read — the function just passes the object as migrations as any to migrate(). Users generating migrations with the new V1 format don't have a journal file and hit a TypeScript compile error:

Property 'journal' is missing in type '{ migrations: {...} }' but required in type '{ journal: ...; migrations: ... }'

Fix

Mark journal as optional (journal?) in the useMigrations parameter type. No runtime behaviour changes — the field was already unused.

[sleitor]

👋 Gentle ping — just checking if this is still on the radar for review. Happy to address any feedback or rebase if needed!

[rvieceli]

Hi @sleitor I think you can remove journal because it has been removed in v1, you can check here https://orm.drizzle.team/docs/upgrade-v1.

[sleitor]

Thanks for the pointer @rvieceli!

Making journal optional (rather than removing it) is intentional for backward compatibility — users on the V0/V1 migration format that include journal in their migration objects will continue to type-check correctly, while V2 migration objects that omit journal will also be accepted.

If the drizzle team prefers to remove it outright (treating V0/V1 format as unsupported in useMigrations), I'm happy to update the PR — just need a signal from a maintainer. Either way the type error reported in #5214 is fixed.