fix: add MFA for WebAuthn bindings

[J0]

What kind of change does this PR introduce?

We introduce bindings for MFA (WebAuthn) which consists of primary methods and helper methods.

Core Methods

The core methods have single step and multi-step use. A single step enroll handles the browser interactions for you while the multi-step enroll provides one the freedom to configure options as they wish.

For enrollment single step looks like:

await supabase.auth. enroll({factorType: 'webauthn'})

While mutli-step enroll contains a webAuthn parameter than can be customized

enroll(factorType: 'webauthn, webAuthn{...}`)

Verify operates in a similar fashion.

There are two methods, challenge and challengeAndVerify which are affected.

Helper methods

We provide the following helper methods for ease of use:

1. browserSupportsWebAuthn - most modern browsers should support the WebAuthn specification.
2. startRegistration - this method takes reference from SimpleWebAuthn and wraps navigator.create. Use this to customize how a credential is created
3. startAuthentication - this methods takes reference from SimpleWebAuthn and wraps navigator.get. Use this to customize how a credential is retrieved

[J0]

Suggested change

	challengeId: string
	challengeId?: string

[J0]

Maybe we should pre-emptively check if web-authn is supported here and return an error if not.