Has anyone gotten the new **Google Cloud Lakehouse catalog federation** Beta (GCP workspaces) to actually run queries?

Setup (followed the docs end to end):
- GCP workspace (us-central1, serverless-only), Unity Catalog
- Previews page: Google Cloud Lakehouse federation toggle ON
- `CREATE CONNECTION ... TYPE GOOGLE_CLOUD_LAKEHOUSE` with a service-account JSON — created fine
- Foreign catalog over it (`warehouse 'bq://projects/<project>'`, authorized paths, storage root) — created fine
- All IAM sorted: the earlier, well-formed permission errors (BigQuery metadata read, GCS object read) appeared and were fixed with grants — so the control-plane path provably reaches our Iceberg metadata in GCS

**The problem — every query, on every engine:**

```
Unrecognized securable kind TABLE_FOREIGN_GOOGLE_CLOUD_LAKEHOUSE
java.lang.IllegalArgumentException
at com.databricks.sql.managedcatalog.client.TypeConversionUtils.toProto(TypeConversionUtils.scala:1960)
at com.databricks.sql.managedcatalog.client.ManagedCatalogClientImpl.updateMetadataSnapshot(...)
at com.databricks.sql.managedcatalog.PermissionEnforcingManagedCatalog.loadForeignSecurableMetadataAndUpdateCache(...)
```

Reproduced identically on:
- DBSQL Serverless — Current channel
- DBSQL Serverless — Preview channel (warehouse restarted after enabling the preview)
- Serverless notebooks/jobs — default environment, and environment client versions 3 and 4
- Two different principals (catalog-owner service principal, and a workspace admin with ALL PRIVILEGES + MANAGE) — same error, so not permissions

It looks like the engines' catalog client simply doesn't have the new securable kind in its enum yet (control plane speaks it, engines don't).

Questions:
1. Has anyone successfully queried a `GOOGLE_CLOUD_LAKEHOUSE` foreign catalog? On which engine/version?
2. Is there a known engine version / rollout timeline for `TABLE_FOREIGN_GOOGLE_CLOUD_LAKEHOUSE` support?
3. Possibly related: on the same workspace, Iceberg tables via **external HMS federation** fail with `Table 'browse_only_table' does not support batch scan` (while an identically-federated plain parquet table reads fine) — same story of an Iceberg-federation preview that the docs describe but the engines refuse. If you've hit either of these and got past them, how?

Any data points appreciated — happy to share more repro details.