fix: improve lightning payment failure messages

[ben-kaufman]

Fixes #736

This PR improves Lightning payment failure error messages by parsing the PaymentFailureReason from LDK-node and displaying user-friendly, actionable messages instead of a generic "Your instant payment failed" toast.

Description

Previously, all Lightning payment failures showed the same generic error message regardless of the actual cause. This made it impossible for users to understand why their payment failed or what action to take.

The PR maps PaymentFailureReason enum values to specific user-friendly messages:

Failure Reason	User Message
RECIPIENT_REJECTED	"The recipient rejected this payment. Try a different amount."
RETRIES_EXHAUSTED	"Could not find a route with sufficient liquidity. Try a smaller amount or wait and try again."
ROUTE_NOT_FOUND	"Could not find a payment path to the recipient."
PAYMENT_EXPIRED	"Payment timed out. Please try again."
Other/Unknown	"Your instant payment failed. Please try again." (original generic message)

Preview

QA Notes

1. Test payment failure messages

1. Open Bitkit with an active Lightning channel
2. Attempt to send a payment to an offline recipient or with an amount that will fail routing
3. Verify the toast message is contextual (not generic)
4. The message should provide actionable guidance

2. Test QuickPay flow

1. Use QuickPay to scan a Lightning invoice
2. If payment fails, verify the error message shown matches the failure type

3. Test background notifications

1. With background notifications enabled, trigger a payment failure
2. Verify the push notification body shows the user-friendly message

4. Regression

• Successful payments should still show success toast
• Payment received notifications should be unaffected

[jvsena42]

insuficient-inbound-recipient.webm

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.