Newly created schema merges into default postgres database on its own

### Description

I am unsure if this is a bug with DBeaver or Postgres (or intended behavior), but after creating a new database and schema, importing data from a CSV file, and reloading the database connection, odd behavior occurs.

The newly created database does not appear in DBeaver (but is present and empty in psql). In addition, the schema and tables appear under the default postgres database instead.

In addition, this problem seems to completely vanish after altering the "Database:" setting in Connection Settings from "postgres" to "Small_Examples" (the name of the database I created). When I revert the setting back to the default "postgres", any new database and tables do not follow the above behavior and are created properly.

I have attached various images of the issue.





As shown, the "Small_Examples" database appears in psql, but is empty. The newly created schema, "company", appears under the default postgres database.

### DBeaver Version

Community Edition 25.0.1.202503302330

### Operating System

Fedora Silverblue 41 / MacOS Sequoia / Windows 11

### Database and driver

PostgreSQL 16.8
PostgreSQL JDBC Driver 42.7.2

### Steps to reproduce

1. Create a new database ("Small_Examples")
2. Create a new schema ("company")
3. Import CSVs into the schema to create new tables
4. Reload the database connection

### Additional context

No extensions loaded, fresh installation of DBeaver and PostgreSQL