displayed Brave wallet address and QR code do not have the same value after restoring wallet

[LaurenWags]

Test plan

1. Create a BAT wallet (does not have to have funds). Save recovery file for this wallet.
2. Set profile aside and create a clean profile.
3. Enable payments, grab screenshots of wallet addresses and QR codes for currencies.
4. restore wallet from step 1.
5. Go to the Add Funds dialog and verify wallet addresses against QR codes.

Original issue description

Description

Sometimes the displayed Brave wallet address (for any currency: BTC, ETH, BAT, LTC) does not match the QR code value. I have only been able to reproduce this on a recovered wallet.

Reported via community: https://community.brave.com/t/alphanumeric-address-qr-code-address-when-i-add-funds/11613

Steps to Reproduce

1. Create a BAT wallet (does not have to have funds). Save recovery file for this wallet.
2. Set profile aside and create a clean profile.
3. Enable payments, grab screenshots of wallet addresses and QR codes for currencies.
4. restore wallet from step 1.
5. Go to the Add Funds dialog and verify wallet addresses against QR codes. QR codes match step 3 but displayed wallet addresses are for the restored wallet.

Actual result:
When backup words are not displayed correctly because you restored your wallet, your QR code address does not match your displayed wallet address.
Ex: Displayed value is in image below. However, if you scan the QR code, you will get a different value of bitcoin:13JoDbYTG9RQZkuDUhtKHY8B7vHAUYa3Ni

Expected result:
These should always match.

Reproduces how often:
easy

Brave Version

about:brave info:
Brave | 0.19.105
rev | 51f8ba5
Muon | 4.5.16

Reproducible on current live release:
Yes

Additional Information

[LaurenWags]

Another way to reproduce this:
Have a wallet created.
Close Brave.
Delete your ledger* files and folders from ~/Library/Application Support/brave
Reopen Brave
New wallet is created.
QR code does not match displayed wallet address.

[srirambv]

Works fine on Windows

[LaurenWags]

Reproduced on MacOS and Win by @srirambv using steps from #12170 (comment)

[NejcZdovc]

@LaurenWags can we close this one and create another issue, because this issue is about recovery, where we reopen it because of the different scenario. Already looking into this second scenario.

[LaurenWags]

Created #12592 and assigned you @NejcZdovc for issue described in #12170 (comment)