bug: Keychain - Disable shielded key import for nano S

[jurevans]

Resolves #1952

• If device is a Nano S, disable shielded key import
• Update Ledger validation to also check against this (zip32 or masp functions only work if both device and version is correct)
• Update warning copy on import

Testing

Build/install extension from this branch, then, assuming you are on > v3.0.0 of the Namada App:

Nano S:

• In setup, import your Ledger
• You should see the warning in the screenshot below
• You should be able to successfully import just the transparent keys

Not-Nano S:

• In setup, import your Ledger
• You should not see any warning
• You are guided through 3 steps: Transparent import, Viewing key import, Proof Gen / Auth key import

Notes

See: https://github.com/LedgerHQ/ledger-live/blob/06cfbf04e2d99e4e7916ace7a10cff8d37c5c38a/libs/ledgerjs/packages/types-devices/src/index.ts#L4

Ledger Live has enumerated the available device IDs here:

/**
 * DeviceModelId is a unique identifier to identify the model of a Ledger hardware wallet.
 */
export enum DeviceModelId {
  blue = "blue",
  nanoS = "nanoS",
  nanoSP = "nanoSP",
  nanoX = "nanoX",
  stax = "stax",
  europa = "europa",
}

Screenshots

NOTE I forced this message by setting the blacklisted device as nanoSP - this should be only be displayed for the nanoS:

[mateuszjasiuk]

Tested and LGTM! Changed deviceId from nanoS to nanoSP for testing!