feat: detect bitcoin/monero uri's

[detherminal]

Closes #1069

Detects URI Schemes for Bitcoin and Monero and uses them.

[detherminal]

Just squashed changes.

[julian-CStack]

Would be better to handle all URIs for all coins. That is somewhat set up already here:

stack_wallet/lib/utilities/address_utils.dart

Line 133 in 5adfee8

static PaymentUriData? parsePaymentUri(

That is already used in several places but mostly just for handling QR code reads such as here:

stack_wallet/lib/pages/send_view/send_view.dart

Line 138 in 5adfee8

Future<void> _scanQr() async {

That _scanQr() function can probably be refactored into two functions. One for the scanning and a second for handing the parsing of the content. That parsing function can then be used on paste as well.

Rather than attempting a full check and parse every time a character is typed it would be better to hook into the on paste event. See https://api.flutter.dev/flutter/material/TextField/contextMenuBuilder.html and https://api.flutter.dev/flutter/material/AdaptiveTextSelectionToolbar-class.html

Finally, this PR only applies to the standard mobile send screen when it should be consistent across all send forms where it would make sense to have this such as on desktop (and possibly some other places as well. Would need to look around the code to find out).

[detherminal]

Would be better to handle all URIs for all coins. That is somewhat set up already here:

stack_wallet/lib/utilities/address_utils.dart

Line 133 in 5adfee8

static PaymentUriData? parsePaymentUri(

That is already used in several places but mostly just for handling QR code reads such as here:

stack_wallet/lib/pages/send_view/send_view.dart

Line 138 in 5adfee8

Future<void> _scanQr() async {

That _scanQr() function can probably be refactored into two functions. One for the scanning and a second for handing the parsing of the content. That parsing function can then be used on paste as well.

Rather than attempting a full check and parse every time a character is typed it would be better to hook into the on paste event. See https://api.flutter.dev/flutter/material/TextField/contextMenuBuilder.html and https://api.flutter.dev/flutter/material/AdaptiveTextSelectionToolbar-class.html

Finally, this PR only applies to the standard mobile send screen when it should be consistent across all send forms where it would make sense to have this such as on desktop (and possibly some other places as well. Would need to look around the code to find out).

I think this contextMenuBuilder does not detect keyboard paste events like Ctrl+P which is almost what everybody use. Do you think it should be that way? This is the way that covers almost all use cases.

[julian-CStack]

Yup, I forgot about the contextMenuBuilder limitation/didn't register when looking it up.

I guess onChanged is the only real option without getting crazy and detecting key press combinations, etc.

It would still be good to do some kind of relatively inexpensive check in onChanged before fully attempting a parse of a uri if possible. Trying to avoid any kind of ui jank while typing (even though paste is almost always going to happen here) is a must. Any ui lag while typing isn't nice.

Everything else in my original comment (besides the contextMenuBuilder stuff) is still valid though I believe

[detherminal]

Seperated the _scanQr function into two pieces as well as the ones in desktop_send.