Extended ASCII database password issue

Database authentication fails when the project database password contains extended ASCII characters. The password is accepted when configuring the project, but the Supabase dashboard is subsequently unable to connect to the PostgreSQL database and reports that the Postgres user could not authenticate. ## Steps to reproduce - Create a Supabase project or change the database password. - Set a password containing extended ASCII characters. - Open the database section in the Supabase dashboard. - The database connection fails with a PostgreSQL authentication error. ## Expected behavior Either: - Extended ASCII characters should work correctly in database passwords. - The UI should reject unsupported characters and clearly state the password requirements. ## Actual behavior - The password is accepted by Supabase, but PostgreSQL authentication fails afterward, making the database inaccessible and unusable through the dashboard. I do not have a screenshot as I have tried to make a new project with a different password that would not containt the extended ASCII (the original one was generated using keepass using characters such as "èFÖÆ" etc) and that project's database works fine.