Migrate vault entries to new schema

[ekzyis]

Description

This PR replaces the existing VaultEntry table which links to a row in the generic Wallet table (and to a row in the users table) with a new table Vault where columns in the specific wallet tables like WalletNWC link to it.

TODO:

• migrate existing vault entries to new schema
• upsertWalletXXX mutation
  • write to new Vault table
  • stop writing to old VaultEntry table
• wallets query
  • read from new Vault table instead of from old VaultEntry table
• remove models.vaultEntry calls
  • injectResolvers
  • getVaultEntries query
  • updateVaultKey mutation
  • clearVault mutation
  • checkWallet job
• remove TODO_newName
• delete VaultEntry table
• Q&A

Screenshots

Additional Context

tbd

Checklist

Are your changes backwards compatible? Please answer below:

tbd

On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:

tbd

For frontend changes: Tested on mobile, light and dark mode? Please answer below:

n/a

Did you introduce any new environment variables? If so, call them out explicitly here:

no

[ekzyis]

I ended up only using get to access properties via a nested path like a.b.c (see tests).

I'll remove the other object helper functions if they don't turn out to be helpful in other places even though they have already been tested.

this isn't outdated, it just says so because I rebased the branch

[ekzyis]

I didn't test the migration with Blink and Phoenixd, only made sure that it looks good so far.

I want to test them with wallets from production since attaching Blink or Phoenixd with only mainnet support is hard in regtest mode.

this isn't outdated, it just says so because I rebased the branch

[ekzyis]

Oh, instead of TODO_newName in the wallet def, I could just use nwcUrl instead of nwcUrlSend. Then the new schema would match the existing typedef. Same for WalletBlink.

[ekzyis]

Dear future @ekzyis, see other comment regarding TODO_newName