Surface "Address not supported" vs "User has rejected transaction" catch

[0xean]

If an invalid address is used we currently catch the error and show the user "User has rejected the transaction" which leads to all sort of confusion.

We should instead catch this specific error and alert the user with "Address 0x123 not supported" on the toast. This will help us and operations to better triage issues of this sort.

[0xean]

bumping prio on this one due to more users coming in the door and more chaos with this issue.

[purelycrickets]

Is there a possibility that a copy button could be added next to the address in the error message?