fix: use SQL for all remote materialized view APIs (#4673)

Remote materialized-view APIs now use SQL for the full lifecycle. Create
and refresh already submit SQL; this change moves describe, paginated
listing, and drop onto `DESCRIBE MATERIALIZED VIEW`, `SHOW MATERIALIZED
VIEWS`, and `DROP MATERIALIZED VIEW`.

Async create, refresh, and drop return the existing Job handle with
`job_type = "query"`. The handle has one `id`: the connection-scoped SQL
query ID, also accepted by `describe_query`. Submission starts the
query, the job drains its result once, and repeated waits reuse the
completed result. Synchronous drop waits for catalog removal; physical
cleanup proceeds in the background.

Listing uses namespace-scoped keyset pagination with opaque resume
tokens. Streamed and deferred SQL responses share the same path. Adds
transport coverage and updates Python/TypeScript documentation for
query-backed drop jobs.

---------

Co-authored-by: Xuanwo <github@xuanwo.io>

nodejs/lancedb/connection.ts

@@ -308,8 +308,8 @@ export abstract class Connection {
   /**
    * Drop the materialized view named `name`.
    *
-   * The view may become unavailable before physical cleanup finishes. Use
-   * {@link dropMaterializedViewAsync} to retain and wait for the cleanup job.
+   * Remote drops wait for the SQL command to remove the catalog binding.
+   * Physical cleanup continues in the background.
    *
    * Rejects a table that exists but is not a materialized view.
    */
@@ -319,8 +319,9 @@ export abstract class Connection {
   ): Promise<void>;
 
   /**
-   * Start dropping the materialized view named `name` and return its cleanup
-   * job without waiting for completion.
+   * Start dropping the materialized view named `name` and return its job.
+   * Remote jobs have type `query` and use the SQL query ID as `id`. Waiting
+   * confirms catalog removal; physical cleanup continues in the background.
    *
    * Rejects a table that exists but is not a materialized view.
    */