LG-11454: Add rename support for face or touch unlock

[aduth]

🎫 Ticket

LG-11454

🛠 Summary of changes

Adds the option for a user to manage (rename or delete) a Face or Touch Unlock authenticator from within the account dashboard, managed inline without the need to navigate to a separate screen.

📜 Testing Plan

1. (Prerequisite) Have an account with Face or Touch Unlock
2. Go to http://localhost:3000
3. Sign in
4. On account dashboard, click "Manage" for Face or Touch Unlock
5. Observe that you are able to manage the authenticator inline
6. Disable JavaScript and repeat steps 4 and 5, verifying that there is feature parity in the no-JavaScript experience

👀 Screenshots

manage-webauthn.mov

[aduth]

Okay, this should be fully code-complete now, and all tests are passing. I've also updated the original comment with a new screen recording after some content and behavior revisions.

I recognize this pull request is very large, coming in just under 3000 lines added. I'll plan to extract some changes to separate pull requests to get this one into a more manageable state, but it's otherwise ready for feedback.

[zachmargolis]

LGTM

[mdiarra3]

Looks good to me as a whole, tested and worked as expected. Also know this will be split up into smaller PRs for easier commenting

[aduth]

There were a couple separate pull requests split from this one:

• Fix concatenation for accessibility matcher error message #9735
• Improve effectiveness of spec JSDOM reset #9737
• LG-11454 (1): Add controllers for WebAuthn management #9742

#9742 was the biggest, and ensures that the route controllers are present during the 50/50 deploy state for when the changes here are deployed.