Generating or copying a receive address with Leather+Ledger should allow the user to confirm the address on device first

[314159265359879]

When a user generates a public address on Ledger Live, it must be displayed on the Ledger device before the address can be copied for use. This allows the user to confirm that the address shown on their computer matches the one displayed on their Ledger device. This adds an extra level of security/certainty that they are using the correct address/key.

We don't currently do this in Leather. We should consider adding this feature.

Some possible solutions

1. We could force the user to check and confirm the address (on device) every time they want to copy the public address (Stacks, Bitcoin).
2. We could also be less forceful and only let users check the address at will, so they can compare what is displayed on their computer screen with what is displayed on the device. We could show a grey checkmark for addresses that have not yet been checked, and then turn it green once it is confirmed. This would both show the user something they can do and, at the same time, not be a requirement if they just want to be mindful of their time.
3. Or do this once for every address when they restore the wallet with their Ledger (or when they set it up for the first time). This last option could be tedious when a user has to confirm 30 addresses (10 Stacks addresses and 2x10 addresses for Bitcoin) every time they restore their wallet, so this would not be my preference. Making the number of accounts to generate flexible (currently fixed at 10) could limit this objection somewhat.

[linear]

LEA-2954 Generating or copying a receive address with Leather+Ledger should allow the user to confirm the address on device first