fix: serialize password confirmation prompts and prioritize strict retries

[joshtrichards]

Summary

Rework password-confirmation prompt handling to support concurrent requests and multiple Axios instances:

• Serialize confirmation requests so each successful validation uses its own dialog session.
• Keep Strict-mode validation pending until the authenticated request response is known.
• Preserve the open dialog for wrong-password responses and prioritize the matching Strict retry.
• Settle the active Strict confirmation and reject queued requests on terminal validation errors, allowing the dialog to close as unsuccessful.
• Track interceptor initialization per Axios instance.
• Avoid logging request configuration objects that may contain the entered password.
• Store Strict-mode tracking metadata under namespaced string config keys so it is preserved across Axios configuration merges and retries.

Testing

• Lax password confirmation succeeds.
• Strict password confirmation succeeds.
• Strict wrong password keeps the dialog open and allows retry.
• Strict terminal request error closes the dialog as unsuccessful.
• Concurrent confirmation requests are handled sequentially.
• Cancelling the dialog rejects the active and queued requests.

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI

TODO

• Test test test
• Review debug logging for additional usefulness in the field
• Fix commits/signing to add AI assistance acknowledgement

Assisted-by: Copilot:gpt-5.6-terra