remote database's migration history does not match local files20250923105350_remote_schema. And I assumed I can finally push my new migration. And so I ran supabase db pull --schema public,auth,storage again. But this time the CLI created a new migration where many of my DB functions were dropped. (p.s. I followed this SO answer to remove all my migrations and start fresh, but it didn't help)