format: expose more catalog/schema/table/column properties

### What feature or improvement would you like to see?

We should make sure we expose everything from JDBC and ODBC, and consider standardizing other common properties, and/or clarifying that drivers may return custom properties of their own choosing (we may want to semi-standardize some of these custom properties by defining a name/type/semantics but not necessarily requiring them to be present).

- BigQuery: https://github.com/adbc-drivers/bigquery/issues/118 (point 10, 11, 12, 13)
- Databricks: https://github.com/adbc-drivers/databricks/issues/236 (point 6)
- PostgreSQL: https://github.com/apache/arrow-adbc/issues/3971 (point 20)
- Trino: https://github.com/adbc-drivers/trino/issues/60 (point 5, 7, 9, 10)

Review the linked BigQuery, Databricks, PostgreSQL, and Trino issues alongside the JDBC and ODBC requirements. Identify which catalog, schema, table, and column properties need standardized names, types, and semantics; done requires an agreed specification, but this issue does not name an implementation entry point or tests.

Written by the indexing model from the issue text.