Use cached outbound value as fallback when node is initializing

[jvsena42]

Replaces #368

Description

• Uses the cached lightning outbound as a fallback in the canSend method if the node is not running
• Add loading state to continue button
• Fix quickpay crash on payment failure
• Skip sync time-out toast error messages
• Set node notification importance as low

Preview

with_amount.mp4

quick_pay.mp4

ln_above_limit.mp4

zero_amount.mp4

QA Notes

• No LN balance -> scan 0 amount uniffied invoice -> use only on-chain balance
• With LN balance -> node syncing -> scan invoice with amount above available > error not enough balance
• With LN balance -> node syncing -> scan 0 amount uniffied invoice > sync success -> enable both balances
• With LN balance -> node synciing > scan 15 amount LN invoice -> sync success > display confirm screen
• With LN balance -> node syncing -> scan invoice with amount above available-> quickpay enabled -> shouldn't pay
• With LN balance -> node syncing -> scan 15 amount LN invoice -> quickpay enabled -> sync success -> should pay

[ovitrif]

Test results

• No LN balance -> scan 0 amount uniffied invoice -> use only on-chain balance 🟢

• With LN balance -> node syncing -> scan LN invoice with amount above available > error not enough balance 🟢

• With LN balance -> node syncing -> scan 0 amount unified invoice > sync success -> enable both balances 🟢

• With LN balance -> node syncing > scan 15 amount LN invoice -> sync success > display confirm screen 🟢

• With LN balance -> node syncing -> scan invoice with amount above available-> quickpay enabled -> shouldn't pay 🟢

• With LN balance -> node syncing -> scan 15 amount LN invoice -> quickpay enabled -> sync success -> should pay 🟠

  • fails for me with handler send error screen "node not setup" ✅ - still ok imho
  • it might've failed because of unexpected force-close