docs: restructure Install nav — shorter group names, A-Z order, fix hosting titles, move dev channels to Maintenance

docs/docs.json

@@ -867,39 +867,40 @@
                 "pages": ["install/index", "install/installer", "install/node"]
               },
               {
-                "group": "Containers and package managers",
+                "group": "Containers",
                 "pages": [
-                  "install/docker",
-                  "install/podman",
-                  "install/nix",
                   "install/ansible",
-                  "install/bun"
+                  "install/bun",
+                  "install/docker",
+                  "install/nix",
+                  "install/podman"
+                ]
+              },
+              {
+                "group": "Hosting",
+                "pages": [
+                  "install/azure",
+                  "install/docker-vm-runtime",
+                  "install/exe-dev",
+                  "install/fly",
+                  "install/gcp",
+                  "install/hetzner",
+                  "install/kubernetes",
+                  "install/macos-vm",
+                  "install/northflank",
+                  "install/railway",
+                  "install/render",
+                  "vps"
                 ]
               },
               {
                 "group": "Maintenance",
-                "pages": ["install/updating", "install/migrating", "install/uninstall"]
-              },
-              {
-                "group": "Hosting and deployment",
                 "pages": [
-                  "vps",
-                  "install/docker-vm-runtime",
-                  "install/kubernetes",
-                  "install/fly",
-                  "install/hetzner",
-                  "install/gcp",
-                  "install/azure",
-                  "install/macos-vm",
-                  "install/exe-dev",
-                  "install/railway",
-                  "install/render",
-                  "install/northflank"
+                  "install/updating",
+                  "install/migrating",
+                  "install/uninstall",
+                  "install/development-channels"
                 ]
-              },
-              {
-                "group": "Advanced",
-                "pages": ["install/development-channels"]
               }
             ]
           },

docs/install/development-channels.md

@@ -4,7 +4,8 @@ read_when:
   - You want to switch between stable/beta/dev
   - You want to pin a specific version, tag, or SHA
   - You are tagging or publishing prereleases
-title: "Development Channels"
+title: "Release Channels"
+sidebarTitle: "Release Channels"
 ---
 
 # Development channels

docs/install/northflank.mdx

@@ -3,7 +3,7 @@ summary: "Deploy OpenClaw on Northflank with one-click template"
 read_when:
   - Deploying OpenClaw to Northflank
   - You want a one-click cloud deploy with browser-based setup
-title: Deploy on Northflank
+title: "Northflank"
 ---
 
 Deploy OpenClaw on Northflank with a one-click template and finish setup in your browser.

docs/install/railway.mdx

@@ -3,7 +3,7 @@ summary: "Deploy OpenClaw on Railway with one-click template"
 read_when:
   - Deploying OpenClaw to Railway
   - You want a one-click cloud deploy with browser-based setup
-title: Deploy on Railway
+title: "Railway"
 ---
 
 Deploy OpenClaw on Railway with a one-click template and finish setup in your browser.

docs/install/render.mdx

@@ -3,7 +3,7 @@ summary: "Deploy OpenClaw on Render with Infrastructure-as-Code"
 read_when:
   - Deploying OpenClaw to Render
   - You want a declarative cloud deploy with Render Blueprints
-title: Deploy on Render
+title: "Render"
 ---
 
 Deploy OpenClaw on Render using Infrastructure as Code. The included `render.yaml` Blueprint defines your entire stack declaratively, service, disk, environment variables, so you can deploy with a single click and version your infrastructure alongside your code.