Retry with differen rp id

[lmuntaner]

Motivation

There are scenarios where the RP ID selected is not the correct one for the device the user is in. When that happens, we want to tell the user to try again, but this time, we will select another RP ID.

In this PR, I introduce the logic to use another RP ID on retry. See the video for a demo of how it looks like.

What I haven't improved in this PR is the UX when retrying. I'm thinking on only improving the toast error for now and if users are confused improve it. But this is an edge case that I hope not so many people will encounter.

Changes

• New helpers excludeCredentialsFromOrigins and hasCredentialsFromMultipleOrigins.
• Add instance variable in Connection: _cancelledRpIds to keep track of the cancelled RP IDs.
• Add logic to use the _cancelledRpIds to filter the devices with the cancelled RP IDs from the calculation to find the next RP ID.

Tests

• Test the new functionality.
• Add tests for excludeCredentialsFromOrigins.

---

🟡 Some screens were changed

[lmuntaner]

Current UX:

The user is logged in the second attempt.
https://github.com/user-attachments/assets/f1b542a9-f945-4a56-a784-fb3ae1969c38

For some reason, github doesn't embed the videos within the comments now...

PENDING: To improve the UX.

[lmuntaner]

@sea-snake @LXIF please review

[LXIF]

LGTM, though would have to spend dedicated time on it if you want me to verify the logic itself more deeply.

[lmuntaner]

LGTM, though would have to spend dedicated time on it if you want me to verify the logic itself more deeply.

the logic is written in the design doc in the section "Algorithm To Choose RP ID". Is that what you mean?