Quack Client: discover server objects (tables, views, etc) using information_schema.tables/information_schema.views and/or duckdb_tables and/or SHOW TABLES

DuckDB 1.5.4.

I set up a quack server and a quack client as per https://duckdb.org/quack/
the client can select from the remote table.

However, when I run ```SELECT * FROM information_schema.tables```, or friends like ```select * from duckdb_tables()``` the remote database does not show up.
I can discover tables using ```SELECT * FROM remote.query('SELECT * FROM information_schema.tables')``` , but I was hoping that is not necessary.

I expected it to work without explicitly calling remote.query, because when I attach a ducklake or iceberg catalog, I can also discover those tables using just a plain query on information_schema.tables. Since access to those was also obtained through `ATTACH`, one would expect that the mechanism for discovering objects would also the same.

Start by reproducing the quack client/server setup and compare information_schema.tables, information_schema.views, duckdb_tables(), and SHOW TABLES with the remote.query workaround. Read the existing catalog-discovery behavior for attached DuckLake or Iceberg catalogs if available in the project; done means remote objects appear in ordinary metadata queries without explicitly calling remote.query.

Written by the indexing model from the issue text.