[iOS] Improve handling of user verification preference and add crash key

We've received reports indicating that the user verification preference
received by a passkey credential request could sometimes be of an
unexpected value.

To make sure that the issue wasn't with the way we were processing the
preference, and also for robustness purposes, this CL uses the
iOS-provided
ASAuthorizationPublicKeyCredentialUserVerificationPreference type (which
is just a `typedef NSString*`), and the different
ASAuthorizationPublicKeyCredentialUserVerificationPreference* constants.

A crash key was also added, so that we can hopefully see what's the
value of the preference when we can't trace it back to one of the
expected values.

Bug: 392239320
Change-Id: Ice06893b97772d8fdd863252da698623f57f6e42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6235188
Commit-Queue: Noémie St-Onge <noemies@google.com>
Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1416456}
NOKEYCHECK=True
GitOrigin-RevId: 30b9157ff55455675b544bffadde328d05ba6b06
5 files changed
tree: f9f90a4da46dd2f3bfeb00eddfbb3a8e0fc923b7
  1. build/
  2. chrome/
  3. components/
  4. google_internal/
  5. intents/
  6. net/
  7. public/
  8. testing/
  9. third_party/
  10. tools/
  11. web/
  12. web_view/
  13. .swift-format
  14. BUILD.gn
  15. COMMON_METADATA
  16. DEPS
  17. DIR_METADATA
  18. features.gni
  19. OWNERS
  20. PRESUBMIT.py
  21. PRESUBMIT_test.py
  22. README.md
README.md

This directory holds code related to Chrome for iOS. See this document for a description of the structure underneath this directory.