Feature Request: Built-in Phone Number Recycling Support for Authentication

Problem When phone numbers are recycled (old number assigned to new person), Supabase Auth prevents linking the recycled number to a new user account, showing the error: AuthApiError: A user with this phone number has already been registered This creates a poor user experience where legitimate users cannot verify their phone numbers simply because the number was previously owned by someone else. Current Workaround The current solution requires: 1. Creating an admin Edge Function to manually unlink phone numbers from previous users 2. Complex client-side logic to coordinate OTP sending and verification with phone unlinking 3. Additional security considerations to prevent abuse Proposed Solution Supabase could implement built-in phone number recycling support with one of these approaches: Option 1: Automatic Unlinking After Successful OTP Verification When a user requests OTP for a phone number already linked to another account Allow OTP to be sent (perhaps wi…