Phone update does not require an otp locally

# 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 To update a user's phone, the following needs to be done: ```ts // 1. user must be logged in // 2. update phone number await supabase.auth.updateUser({ phone: "new phone" }) // 3. user inputs otp they received await supabase.auth.verifyOtp({ phone: "new phone", token: "...", type: "phone_change" }) ``` However locally, calling `updateUser` updates the `auth.users` row directly. I tested on a test hosted supabase instance and it worked as intended fyi. ## To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Have Supabase configured locally using the CLI and running 2. Create a user using phone provider 3. Login then call ```ts await supabase.auth.updateUser({ phone: "new phone" }) ``` 5. Check the `auth.users` table and see `phone` is updated directly ## Expected behavior Locally, `auth.users` row columns should be updated with phone change stuff and an otp should be sent. ## System information - OS: Win 11 - Version of supabase-js: 2.43.5 - Version of Node.js: 20.11.1