Signing in via sms otp registers new sign up in Auth reports.

# Bug report <!-- ⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first: - Docs: https://docs.supabase.com - Discussions: https://github.com/supabase/supabase/discussions - Discord: https://discord.supabase.com Before opening a bug report, please verify the following: --> - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug I got only phone provider enabled for my app. I want user to be seamlessly signed up after providing correct otp. That's why I use following code in my auth form handler: ```js await supabaseClient.auth.signInWithOtp({ phone: formData.phone, options: { shouldCreateUser: true, channel: 'sms', }, }); ``` then I redirect the user to otp page and call following function to verify the otp: ```js await supabaseClient.auth.verifyOtp({ type: 'sms', phone: phoneNumberForOtp, token: otp, }); ``` When user that is already present in database signs in, I get new sign-up event in auth report: <img width="1914" height="616" alt="Image" src="https://github.com/user-attachments/assets/9dd22d75-fb33-4992-817f-0ee034afb4de" /> ## To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Enable only phone provider for your app 2. Use `signInWithOtp` with `shouldCreateUser: true` option, and `verifyOtp` to sign in existing user. 3. Go to Supabase dashboard/Reports/Auth 4. New sign up event is registered. ## Expected behavior It should register sign-in event instead of sign-up since the user was already present in database. ## Screenshots // Provided in description section ## System information - OS: macOS - Browser: chrome - Version of supabase-js: `2.50.3`…