[leonvogt]

In the process of enabling passkey support to our apps, I've noticed that, passkey through the WebView works out-of-the box in iOS, but needs a small tweak in Android.
More specifically, one needs to create a custom WebView to enable WebSettingsCompat.setWebAuthenticationSupport().

This PR would make that obsolete. Hotwire Native will enable web authentication support, if the user opts in via Hotwire.config.webAuthenticationEnabled.
It defaults to false, same as the WebView itself.

---

For people who read this and are in the process of integrating passkeys:

1. Make sure you have a Digital Asset Links association with the site (delegate_permission/common.get_login_creds)
2. Only works with exactly those associated sites. So no localhost or self signed sites.
3. The WebView sends the app identity as the WebAuthn origin (android:apk-key-hash:<hash>) rather than the web origin, so the server has to accept that too.

[rafaeldev]

How about add a DEBUG log to check early return?

[leonvogt]

Good idea!

[leonvogt]

Hm, after thinking more about it, it might be a bit spammy to add a debug log here.

Since this code doesn't run only when webAuthentication is needed, but instead runs every time a WebView is created, and since most people don't use passkeys, I don't think such a debug log would be useful for the majority of devs.

If the code only executed when needed, like for camera or location permissions, I think such a debug log would be a great thing.