docs: keep availability summaries readable in the comparison

Four summaries pointed at the table or sections below, which reads wrongly as a row of the comparison. They now stand alone, and insert links to its bulk-ingest section.

docs/web/ingestion/insert.mdx

@@ -8,8 +8,8 @@ availability:
   enterprise: available
   summary: >-
     Rows are appended in the embedded library and on a deployment. Large writes
-    to a deployment are uploaded in parts, which the section on bulk ingests
-    explains how to tune.
+    to a deployment are uploaded in parts; see
+    [Bulk ingests into a remote table](#bulk-ingests-into-a-remote-table).
 ---
 
 Rows are appended with `table.add()`. It accepts the same shapes

docs/web/management/database.mdx

@@ -10,7 +10,7 @@ availability:
   summary: >-
     The embedded library connects to a local directory or object storage, and
     a `db://` URI connects to a deployment. Which operations exist depends on
-    the connection, as the table below shows.
+    the connection.
 ---
 
 A database is the root of a [catalog](/basics/catalog). A connection opens

docs/web/management/table.mdx

@@ -10,7 +10,7 @@ availability:
   summary: >-
     Tables are created, evolved, versioned and dropped in the embedded library
     and on a deployment. Renaming, cloning, dropping every table and pruning old
-    versions differ between the two, as their sections say.
+    versions differ between the two.
 ---
 
 import {

docs/web/search/index.mdx

@@ -9,7 +9,7 @@ availability:
   summary: >-
     Vector, full-text and hybrid search run in the embedded library and against
     a deployment. Reading very large results and probe tuning differ between the
-    two, as the sections below note.
+    two.
 ---
 
 | Feature | Description |