docs: split SDKs and SQL into two pages, promote to Getting Started

SQL now leads with why you'd reach for it beyond analytics: it's served over
Flight SQL, so it's the way in for any language without a native LanceDB SDK,
and broadly every public SDK method has a corresponding SQL statement. Closes
by pointing at the SQL Reference as the spec that defines the precise
behavior behind both the SQL surface and the SDK operations it mirrors.

Moving both into Getting Started (before Agentic Skills) means a reader knows
what the API surface even is before being told how to hand it to an agent.

docs/web/sql/data-types.mdx

@@ -75,7 +75,7 @@ SELECT id FROM documents WHERE vector IS NOT NULL
 <Warning>
 Arithmetic over it is **list** arithmetic. There is no SQL similarity operator
 and no SQL form for vector search — run the search in an SDK and use SQL over
-its result. See [SDKs and SQL](/basics/apis#no-vector-sql).
+its result. See [SQL](/basics/sql#no-vector-sql).
 </Warning>
 
 ### JSON {#json}

docs/web/sql/index.mdx

@@ -8,7 +8,7 @@ keywords: ["sql", "datafusion", "flight sql", "reference", "dialect"]
 
 <Badge color="red">Enterprise</Badge> SQL runs on a deployment. A local database
 has no engine to plan a statement, so `execute_query` raises there -- see
-[SDKs and SQL](/basics/apis).
+[SQL](/basics/sql#sql-is-remote).
 
 This is a reference rather than a guide: one page per construct, syntax first.
 The guides elsewhere in these docs show the same operations from the SDKs.