Don't error out because of UxUpdate messages

[msirringhaus]

The UsbStateInternal::NeedsUserVerification-case prevented the fallback from fingerprints to PINs, in case UV got blocked by using the wrong finger too often.
In general, I don't think we should error out because of UxUpdates at all, as libwebauthn should error out properly in case of actual errors in the actual function call (not via the updates channel).
With this patch, I'm able to fall back to entering PINs after UV got blocked. However, once PINs get blocked also, the UI doesn't reflect that, but I think this is a general issue right now with propagating/displaying errors of any kind.
Sadly, I didn't have the time to add a fix for that to this PR, too.

[iinuwa]

sorry for not getting to this for a while.

In general, I don't think we should error out because of UxUpdates at all, as libwebauthn should error out properly in case of actual errors in the actual function call (not via the updates channel).

I see. you're referring to this here: https://github.com/linux-credentials/libwebauthn/blob/d3cd0d3bfd237ad4dc77ce7017b9c34588986182/libwebauthn/src/webauthn.rs#L463-L490. So libwebauthn will send a new PresenceRequired update after receiving UV Blocked from the authenticator? This sounds good.