docs: move versioning and branching under Table, split schema from data evolution

Versioning and branching are properties of a table, not steps in getting data
in, so they join the Table group. Consistency stays with Ingestion, where the
question it answers -- when do other writers' rows become visible -- is asked.

The Ingesting Data page was in the Table group while an Ingestion overview
existed separately, so the two are merged. The large-dataset section was
duplicated between it and the insert page; the insert page keeps it.

Schema and Data Evolution covered two different things under one title.
Changing a table's shape stays in Table management; deriving values from data
already there becomes a Feature engineering page, next to computed columns and
functions, which are the same job at larger scale.

docs/web/docs.json

@@ -70,6 +70,10 @@
     {
       "source": "/feature-engineering/functions",
       "destination": "/management/function"
+    },
+    {
+      "source": "/tables/create",
+      "destination": "/ingestion"
     }
   ],
   "navigation": {
@@ -110,9 +114,10 @@
                 "group": "Table",
                 "pages": [
                   "tables/index",
-                  "tables/create",
                   "tables/schema",
-                  "tables/multimodal"
+                  "tables/multimodal",
+                  "tables/versioning",
+                  "tables/branching"
                 ]
               },
               "management/function"
@@ -126,8 +131,6 @@
               "ingestion/merge-insert",
               "ingestion/update",
               "ingestion/delete",
-              "tables/versioning",
-              "tables/branching",
               "tables/consistency"
             ]
           },
@@ -169,6 +172,7 @@
             "group": "Feature engineering",
             "pages": [
               "feature-engineering/index",
+              "feature-engineering/data-evolution",
               "feature-engineering/add-computed-column",
               "feature-engineering/refresh-column",
               "feature-engineering/materialized-views"