[WIP] Clean up Troubleshoot (docs freeze MVP) (#485)

[Preview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/485/troubleshoot/)

Get things into a reasonable state for the docs thaw:

- Make titles and nav titles consistent
- Reflect the order of other sections and the overall IA
- NOTE: I moved topics in the TOC but not files in the directories --
coming in separate PR 😓
- Add landing page / roundup topics
- Add entrypoint skeleton / template
- Sprinkle WIP notes 🧂 
- Change generic `{adomonition}`s to `{tip}`s

part of elastic/docs-projects#434

Author: marciw

troubleshoot/deployments.md

@@ -5,6 +5,12 @@ mapped_pages:
 
 # Ask for help [ece-getting-help]
 
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on moving this content to the [Troubleshooting overview](/troubleshoot/index.md). 
+:::
+
 For issues with Elastic Cloud Enterprise that you cannot fix yourself …​ we’re here to help!
 
 If you are an existing Elastic customer with a support contract, please create a ticket in the  [Elastic Support Portal](https://support.elastic.co) and provide an ECE [diagnostics package and log files](../../../deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md). By providing a diagnostics package, you make it easier for us to help you.

troubleshoot/deployments/cloud-enterprise/ask-for-help.md

@@ -1,10 +1,17 @@
 ---
+navigation_title: "Elastic Cloud Enterprise"
 mapped_urls:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-find.html
 ---
 
-# Elastic Cloud Enterprise
+# Troubleshoot Elastic Cloud Enterprise
+
+:::{admonition} WIP
+⚠️ **This page is a work in progress.** ⚠️
+
+The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure.
+:::
 
 ## Finding deployments [ts-ece-find]
 

troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Zookeeper quorum"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-zookeeper-quorum.html
 ---

troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md

@@ -1,9 +1,10 @@
 ---
+navigation_title: "Removing containers"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-uninstall.html
 ---
 
-# Remove Elastic Cloud Enterprise [ece-uninstall]
+# Remove Elastic Cloud Enterprise containers  [ece-uninstall]
 
 You might need to remove Elastic Cloud Enterprise for one of the following reasons:
 
@@ -14,23 +15,18 @@ You remove Elastic Cloud Enterprise by removing all containers on the host:
 
 * If using Docker
 
-::::{admonition} 
+
 ```sh
 docker rm -f frc-runners-runner frc-allocators-allocator $(docker ps -a -q); sudo rm -rf /mnt/data/elastic/ && docker ps -a
 ```
 
-::::
-
 
 * If using Podman
 
-::::{admonition} 
 ```sh
 sudo podman rm -f frc-runners-runner frc-allocators-allocator $(sudo podman ps -a -q); sudo rm -rf /mnt/data/elastic && sudo podman ps -a
 ```
 
-::::
-
 
 If you plan to reinstall Elastic Cloud Enterprise on the host, make sure you [delete the host](../../../deploy-manage/maintenance/ece/delete-ece-hosts.md) from the Cloud UI first. Reinstallation can fail if the host is still associated with your old Elastic Cloud Enterprise installation.
 

troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Diagnostics"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-run-ece-diagnostics.html
 ---

troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md

@@ -1,9 +1,10 @@
 ---
+navigation_title: "Container engines"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-containers.html
 ---
 
-# Troubleshooting container engines [ece-troubleshooting-containers]
+# Troubleshoot container engines [ece-troubleshooting-containers]
 
 This article describes how to troubleshoot container engine services in Elastic Cloud Enterprise. We refer to [Docker](https://www.docker.com/) by default, as it’s the most common container engine, but these steps are also valid for [Podman](https://podman.io/). You can simply replace `docker` in the commands  with `podman` as needed.
 

troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md

@@ -1,4 +1,5 @@
 ---
+navigation_title: "Emergency roles token"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-emergency.html
 ---

troubleshoot/deployments/cloud-enterprise/use-emergency-roles-token.md

@@ -1,9 +1,10 @@
 ---
+navigation_title: "ZooKeeper sync status"
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-zookeeper-sync.html
 ---
 
-# Verify ZooKeeper Sync Status [ece-zookeeper-sync]
+# Verify ZooKeeper sync status [ece-zookeeper-sync]
 
 It is recommended to check the ZooKeeper sync status before starting any maintenance on your Director nodes. This helps you prevent the following scenarios:
 

troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md

@@ -1,9 +1,12 @@
 ---
+navigation_title: "Common issues"
+applies:
+  eck: all
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-common-problems.html
 ---
 
-# Common problems [k8s-common-problems]
+# Troubleshoot common Elastic Cloud on Kubernetes issues [k8s-common-problems]
 
 
 ## Operator crashes on startup with `OOMKilled` [k8s-common-problems-operator-oom]