Re-enable foreign key support if needed when a migration fails

[eygraber]

No description provided.

[Copilot]

Pull Request Overview

This PR ensures that foreign key constraints are properly re-enabled when database creation or migration operations fail. The change addresses a scenario where foreign keys could remain disabled if an exception occurs during these operations.

• Adds exception handling to re-enable foreign keys when creation/migration fails
• Refactors foreign key violation reporting into a separate function
• Adds comprehensive test coverage for exception propagation and foreign key state recovery

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
AndroidxSqliteDriver.kt	Implements try-catch block to re-enable foreign keys on exception and extracts foreign key violation reporting
AndroidxSqliteMigrationTest.kt	Adds tests for exception propagation and foreign key re-enabling during migration failures
AndroidxSqliteCreationTest.kt	Adds tests for exception propagation and foreign key re-enabling during creation failures

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}