Supabase Auth API leaks connections

# Bug report - [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 This is a bug created by Supabase, not by our application. Seems like you broke something in the last few weeks, as this is a recent problem caused by Supabase forcing its updates on my system when I did a `supabase db reset` for local development. In your new Auth API, you seem to be creating a new database connection for every single authentication request. I have run into issues with your API while testing Supabase locally. Invoking the Auth API sign up or sign in functions at scale causes it to exhaust system resources and seize up, breaking the ability for users to sign in. ## To Reproduce 1. Sign in many users in a short period of time https://supabase.com/docs/reference/javascript/v1/auth-signin ## Expected behavior Auth tokens should be generated for each user. ## Actual behavior Auth API breaks down. ``` {"component":"api","error":"error finding user: failed to connect to `host=supabase_db_base user=supabase_auth_admin database=postgres`: dial error (dial tcp [172.18.0.2:5432](http://172.18.0.2:5432/): connect: cannot assign requested address)","grant_type":"password","level":"error","method":"POST","msg":"500: Database error querying schema","path":"/token","referer":"http://localhost:5173/","remote_addr":"192.168.65.1","request_id":"e95f7e1e-6eb6-404a-9b29-a033dc57ef8d","time":"2025-12-03T04:18:47Z"} ```