[PM-13932] Fix passkey flow incorrect routing

[rr-bw]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-13932

📔 Objective

This PR fixes a bug in the LockComponent refresh that affected the use and setup/save passkey flows.

Description of the bug: When a locked user attempts to sign in with a passkey on a website, when they unlock they are incorrectly navigated to their vault, rather than to the "Login with passkey" screen (the /fido2 route). This forces them to re-initiate the sign in with passkey flow on the website, at which point they can now access the passkey in Bitwarden since they are unlocked.

The correct flow is that when they unlock they should to be taken to the "Login with passkey" screen and allowed to use their passkey.

The fix for this involved three changes, which I've explained in a comment next to each of the code changes.

The two videos below show the before and after-fixed version of using a passkey. Note that I also tested the setting up/saving a passkey flow as well, and it works.

📸 Screenshots

🐞 Before (bug version)

before.mov

✅ After (fixed version)

after.mov

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 33.37%. Comparing base (2da3043) to head (39dbe81).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...r/src/auth/functions/unauth-ui-refresh-redirect.ts	0.00%	0 Missing and 1 partial ⚠️
...bs/angular/src/utils/extension-refresh-redirect.ts	0.00%	0 Missing and 1 partial ⚠️
libs/auth/src/angular/lock/lock.component.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #12363   +/-   ##
=======================================
  Coverage   33.36%   33.37%           
=======================================
  Files        2908     2908           
  Lines       90989    90990    +1     
  Branches    17328    17328           
=======================================
+ Hits        30363    30369    +6     
+ Misses      58223    58217    -6     
- Partials     2403     2404    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Checkmarx One – Scan Summary & Details – 6c2a8053-b4d0-413a-adc1-be0bf87dbce5

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Client_Privacy_Violation	/apps/cli/src/commands/get.command.ts: 151	Attack Vector

[JaredSnider-Bitwarden]

Excellent work.

[quexten]

Has been already merged but excellent work! This also fixed https://bitwarden.atlassian.net/browse/PM-16116.