feat(plugins): add SSH tunnel to Weaviate, Typesense and Elasticsearch

[datlechin]

Why

The connection form for Weaviate had no SSH tunnel, so a node on a private server could not be reached the way Postgres can. Typesense and Elasticsearch had the same gap. Each driver declared no SSH when it was added, with no technical reason: all three are one HTTP port on a self-hosted server, the same shape as Trino and SurrealDB, which already tunnel.

Change

• Weaviate, Typesense and Elasticsearch offer SSH Tunnel, Cloudflare Tunnel, SOCKS proxy and tunnel command. The drivers need no change: each dials the forwarded port and already skips the certificate check the tunnel drops.
• Cloudflare Tunnel now follows SSH, like SOCKS and tunnel command. Before a plugin was installed, BigQuery, DuckDB, DynamoDB and seven other types offered it with nothing to forward.
• Docs list the new transports and fix the SSH exclusion list.

Verified

PortForwardCapabilityTests and the new ConnectionFormTransportTests cases fail on main (10 types leak Cloudflare Tunnel) and pass here.

Not in this PR

• The option appears for installed plugins once plugin-weaviate, plugin-typesense and plugin-elasticsearch are released.

Fixes #3277

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
TablePro	🟢 Ready	View Preview	Oct 7, 2026, 11:56 AM

💡 Tip: Enable Automations to automatically generate PRs for you.