desktop: "Sign in with a passkey" and "Sign in with your browser" are two buttons mapped to the same action? (when passkeys are unavailable)

unsure if step 0 is necessary at all.

0. Do Not Have a passkey provider on your desktop session (e.g. i use Bitwarden, which supports it on mac/windows, but not on linux, so i can only use those passkeys in the browser extension)
1. try to add an account
2. select the instance

There should be an option to "Sign in with your browser", and a "Sign in with a passkey" button that tries to use the native passkeys, and will fail. Better yet, the button could be grayed out with a note that "passkeys are not supported on this system".

There are the two expected buttons, but both perform the exact same action that i'd expect from just the "Sign in with your browser" button. The one labeled "Sign in with a passkey" triggers browser handoff.

Stable Desktop 2026.1101.230756, Web 2026.1101.230756, Linux 6.18.55 (x64), Electron 44.9.1, Chrome 152.0.7977.167, Node 24.22.0, Locale en-US

The video shows #4706 when refreshing an expired session, then 12 seconds in, it goes to the "Use another account" view (step 1. for reproducing this bug), followed by selecting an instance (step 2.), then it clearly shows the described redundancy in the UI. it clicks both buttons, and flips between the browser tabs to show that they really did do the exact same thing. It then goes on to log in and expire that session to show #4709.