Add nice UX when passkey is not found in that RP ID

[lmuntaner]

Motivation

The algorithm to choose RP ID is not bulletproof. For those scenarios that the user needs to retry, we want to guide the user a bit.

In this PR, the UX is improved by showing an info toast encouraging the user to try again.

Changes

• Add new return type PossiblyWrongRPID to the login and fromWebauthnCredentials methods.
• Manage the new return type and show a toast info if so.

Tests

• Tested in beta domains. See screen video.
• Change current test for the scenario that has been changed.

---

🟡 Some screens were changed

[lmuntaner]

UX:

Screen.Recording.2024-12-18.at.12.50.52.mov

New toast:

[lmuntaner]

@LXIF @sea-snake please review

[LXIF]

LGTM technically, though admittedly wording is confusing - users may not know we have multiple domains and that passkeys are separated by domain.

[lmuntaner]

LGTM technically, though admittedly wording is confusing - users may not know we have multiple domains and that passkeys are separated by domain.

I agree. Thankfully, this is an edge case that I hope not many people will encounter.

I'm also open to other wordings, but this was the best I could think of. We can always change before enabling the flag in mainnet.