Move LaunchDarkly under Track Config Changes to match master

LaunchDarkly was originally a child of Track Config Changes on master,
not Send Alerts. Move it there by adding a toctree to
kubernetes-changes.rst and removing it from configuration/index.rst.

https://claude.ai/code/session_0184fwhrjC4ELrYQBMCbyhfS

Author: claude

docs/configuration/index.rst

@@ -26,7 +26,6 @@ Connect your monitoring system to Robusta, to enrich alerts and apply automation
    alertmanager-integration/newrelic
    alertmanager-integration/pagerduty-alerting
    alertmanager-integration/solarwinds
-   alertmanager-integration/launchdarkly
    alertmanager-integration/customize-labels-priorities
    exporting/custom-webhooks
 
@@ -127,11 +126,6 @@ Other
         :link: alertmanager-integration/solarwinds
         :link-type: doc
 
-    .. grid-item-card:: :octicon:`pulse;1em;` LaunchDarkly
-        :class-card: sd-bg-light sd-bg-text-light
-        :link: alertmanager-integration/launchdarkly
-        :link-type: doc
-
 Advanced
 ---------
 

docs/track-changes/kubernetes-changes.rst

@@ -1,6 +1,12 @@
 Kubernetes Changes
 ==================
 
+.. toctree::
+   :maxdepth: 1
+   :hidden:
+
+   LaunchDarkly <../configuration/alertmanager-integration/launchdarkly>
+
 When using Robusta SaaS, Robusta automatically tracks all Kubernetes changes and correlates them with alerts.
 
 This provides context about recent changes when investigating issues, helping you quickly identify if a deployment, configuration update, or other change caused a problem.