feat: Add My Account API support for managing authentication methods

[subhankarmaiti]

Summary

• Adds My Account API client (myAccount property) for managing user authentication methods
• Supports passkey enrollment (challenge + verify), phone, email, TOTP, push notification, and recovery code enrollment with OTP/non-OTP confirmation
• Adds CRUD operations for authentication methods (get, list, update, delete) and factor listing
• Introduces MyAccountError class exposing type, title, detail, and statusCode properties matching native SDK error surfaces
• Implements native bridge layer for both iOS (Swift) and Android (Kotlin)
• Uses per-call accessToken pattern for thread safety (no cached client)

New Public API

• myAccount.passkeyEnrollmentChallenge({ accessToken, ... })
• myAccount.enrollPasskey({ accessToken, ... })
• myAccount.enrollPhone({ accessToken, phoneNumber, preferredAuthenticationMethod? })
• myAccount.enrollEmail({ accessToken, emailAddress })
• myAccount.enrollTOTP({ accessToken })
• myAccount.enrollPushNotification({ accessToken })
• myAccount.enrollRecoveryCode({ accessToken })
• myAccount.confirmPhoneEnrollment({ accessToken, id, authSession, otpCode })
• myAccount.confirmEmailEnrollment({ accessToken, id, authSession, otpCode })
• myAccount.confirmTOTPEnrollment({ accessToken, id, authSession, otpCode })
• myAccount.confirmPushNotificationEnrollment({ accessToken, id, authSession })
• myAccount.confirmRecoveryCodeEnrollment({ accessToken, id, authSession })
• myAccount.getAuthenticationMethods({ accessToken, type? })
• myAccount.getAuthenticationMethodById({ accessToken, id })
• myAccount.updateAuthenticationMethodById({ accessToken, id, name?, preferredAuthenticationMethod? })
• myAccount.deleteAuthenticationMethodById({ accessToken, id })
• myAccount.getFactors({ accessToken })

Error Handling

• Passkey methods throw PasskeyError
• All other My Account methods throw MyAccountError

Test plan

• Verify TypeScript compiles (npx tsc --noEmit)
• Test passkey enrollment flow on iOS 16.6+
• Test phone/email enrollment + OTP confirmation
• Test TOTP enrollment + confirm with authenticator code
• Test recovery code enrollment + confirm
• Test get/update/delete authentication methods
• Test getFactors

[pmathew92]

Would a single authentication method suffice or do you think we can have granular authentication methods for each factors inheriting from a common interface. Let me know your thoughts?

[subhankarmaiti]

Granular would be better, But none of our native SDK is doing that today. So making it similar to the Native SDKs

[pmathew92]

https://github.com/auth0/Auth0.Android/blob/main/auth0/src/main/java/com/auth0/android/result/AuthenticationMethod.kt
Android has this

[subhankarmaiti]

But for swift we do not have this, we can handle it later I feel, as improvement.
ref: https://github.com/auth0/Auth0.swift/blob/master/Auth0/MyAccount/AuthenticationMethods/GetAuthenticationMethodsResponse.swift