LG-14814: Entering TOTP code in wrong format shows error text mentioning phone

[aduth]

🎫 Ticket

LG-14814

🛠 Summary of changes

Fixes an issue where entering TOTP (Authentication App) code in the wrong format shows an error message mentioning a code "sent to your phone".

This is related to LG-13450 (#10898), where we changed the error message, intending it to apply for phone-sent codes (OTP via SMS or Voice), but shared code between phone OTP and TOTP caused the error to be used in both places.

The solution here is to restore the shared code instance to use generic language, and override to use the phone-specific languages in those use-cases.

📜 Testing Plan

Verify TOTP invalid format shows generic message:

1. Prerequisite: Have an account with authentication app as MFA method
2. Go to http://localhost:3000
3. Sign in
4. (If not prompted for MFA, click "Forget all browsers", confirm, sign out, and start from Step 2)
5. (If not prompted for TOTP as MFA, click "Choose another authentication method", and then select and submit "Authentication app")
6. Enter code in an invalid format, e.g. "12345" (too few characters)
7. Submit
8. See error message "Enter your entire one-time code without spaces or special characters"

Verify no regressions in phone OTP invalid format showing specialized message:

1. Prerequisite: Have an account with phone as MFA method
2. Go to http://localhost:3000
3. Sign in
4. (If not prompted for MFA, click "Forget all browsers", confirm, sign out, and start from Step 2)
5. (If not prompted for phone as MFA, click "Choose another authentication method", and then select and submit "Text message")
6. Enter code in an invalid format, e.g. "12345" (too few characters)
7. Submit
8. See error message "Enter the one-time code sent to your phone. Do not use spaces or special characters."

👀 Screenshots

MFA	Before	After
TOTP
Phone