Better visibility into migration issues

[piyalbasu]

Follow up to ticket #2176

Currently, when we update our data layer in the extension, a user must go through a series of migrations in order to make sure the user's current schema matches what is intended by the application code. We do not have visibility when a user hits an error with this migration and/or if a user's schema is malformed.

Acceptance Criteria:

1. Add sentry alerting when a migration fails to give visibility into problematic migrations
2. Add a schema check at the end of the migration chain to see if a user's schema is correct. If not, send an alert to Sentry with the missing key/values to give us more info about a possible missing piece of info a user needs
3. Add Amplitude tracking for a user's data storage version and their extension version to see how many users have mismatched extension and data storage versions

[Keeeeeeeks]

9/22 update: We want to distinguish between:

1. Detecting the error (this ticket)
2. Fixing the error (another ticket)

Sizing: 2 Priority: P1-flex Reasoning: It's a blocking error (if a malformed user schema blocks them from transacting, or seeing their balance, the only way to fix it is uninstalling, reinstalling, and reimporting their wallet. bad UX)