bug/353 - Ledger error-handling improvements

[jurevans]

Resolves #353

Any time an error is encountered with the Ledger device, the extensions should always allow the user to correct the issue and proceed. A locked device or unloaded app should not force the user to refresh! Also, the appropriate error should be reported to user in each case!

• Connect Ledger
  • Recovers from device locked
  • Recovers from app not loaded
  • Recovers from device not plugged in, or device not initially unlocked (same error: "Access Denied")
• Add Account
  • Recovers from device locked
  • Recovers from app not loaded
  • Recovers from device not plugged in, or device not initially unlocked (same error: "Access Denied")
• Reveal PK
  • Does not proceed to next transaction if any errors are encountered (including tx rejection)
• Submit Tx (Reveal PK, Bond, Unbond, Withdraw, Transfer)
  • Recovers from device locked
  • Recovers from app not loaded
  • Recovers from transaction rejected
  • Recovers from device not plugged in, or device not initially unlocked (same error: "Access Denied")

[github-actions]

🚀 Deployed on https://pull-request-363--wallet-development-heliax-dev.netlify.app

[mateuszjasiuk]

Tested! Looks good to me :)