SQLWallet: Test the schema/data equivalence for the supported SQL databases

[mohamedawnallah]

Description

Towards #1119.

Motivation and Context

Especially helpful for Address Manager SQLization #1098 and #1103 that @GustavoStingelin's currently working on.

Design Approach

1. Creating PostgreSQL DB {1} (DESTINATION) from native PostgreSQL migrations
2. Creating SQLite DB (SOURCE) from SQLite migrations
3. Migrating SQLite → PostgreSQL DB {2} (DESTINATION) via pgloader
4. Comparing PostgreSQL DB {1} vs PostgreSQL DB {2} schemas
5. If schemas match → SQLite ≡ PostgreSQL (transitively)
6. Schema equivalence → Future data compatibility guaranteed (same structure = same data types, constraints, and behavior)

Pull Request Checklist

🤖 AI Assistance Disclosure

If you used AI assistance (e.g., Copilot, ChatGPT, etc.) to generate any code, documentation, descriptions, or other artifacts in this PR, please answer the following questions:

• On a scale from 0 to 10, how thoroughly did I review the AI-generated artifacts?

  • Rating: [Inserting a number from 0 to 10]
  • 0 = Didn't review at all, copy-pasted directly
  • 5 = Skimmed through, made some basic checks
  • 10 = Line-by-line review, tested thoroughly, fully understand every aspect

• On a scale from 0 to 10, how well do the resulting artifacts represent me as the author - my understanding, judgment, and quality standards?

  • Rating: [Inserting a number from 0 to 10]
  • 0 = This is purely AI output, doesn't reflect my work
  • 5 = Partially reflects my standards, some areas I'm uncertain about
  • 10 = Fully represents my work, could have written this myself

• (Optional) If I'm open to sharing: How did I use AI to create the resulting artifacts?

  • Usage: [Describing how you used AI, e.g., "Used AI to generate initial boilerplate, then I heavily modified the logic and added custom error handling."]