Misc Bolt12/LN address resolution bugs on flaky network

[kilrau]

Did some tests on flaky network. Tl;dr: we should have a generic network error catching all of the below:

First:

Couldn't capture it in a screenshot, but UI showed the red error popup with [object object]:

Second:

Also, on flaky internet this "invalid invoice" error can happen and it enters "undefined" in the invoice field. Should instead error with the generic network error and keep the lightning address/bip353 in the invoice field, so the user can hit "Create Atomic Swap" to try again:

Third:

If Boltz fails our swap creation POST with 400 for whatever reason, result is the MRH liquid address pasted as destination. BUT address validation is not triggered, so it shows as invalid. As it's confusing why my submarine swap suddenly changed into a chain swap to an unknown liquid address, I'd also want to catch this and error with the generic network error and keep the original lightning address/bip353 to try again: