Extended ASCII Characters In Database Passwords Cause PostgreSQL Authentication Failure

The password string containing non-ASCII characters is likely mishandled during storage or transmission between Supabase components and PostgreSQL, leading to a mismatch in the byte representation used for SCRAM/MD5 authentication.

1. Create a Supabase project or change the database password. 2. Set a password containing extended ASCII characters (e.g., 'èFÖÆ'). 3. Open the database section in the Supabase dashboard. 4. Observe that the database connection fails with a PostgreSQL authentication error.

This frontend-only fix can be bypassed by direct API calls, so it is not a complete solution. The underlying encoding issue in the password management pipeline must be fixed. Existing users with non-ASCII passwords will remain locked out until they reset their password via a supported flow. Rolling back this change would revert to the original behavior; ensure the backend fix is deployed before removing the validation. No concurrency or threading issues are introduced, but the ASCII restriction may reject some characters users expect to be valid.