remove used upgrade files, add missing mapping

Author: shainaraskas

deploy-manage/upgrade/orchestrator/re-running-the-ece-upgrade.md

@@ -1,3 +1,7 @@
+---
+mapped_pages:
+- https://www.elastic.co/guide/en/cloud-enterprise/current/ece_re_running_the_ece_upgrade.html
+---
 # Re-running the ECE upgrade [re-running-ece-upgrade]
 
 By default, re-running the `elastic-cloud-enterprise.sh upgrade` command resumes the previous ECE upgrade process. However, if your previous ECE upgrade attempt got stuck (for example, due to infrastructure problems, a host going offline, or similar) and re-attempting the upgrade still results in the upgrade process being blocked, run `elastic-cloud-enterprise.sh upgrade --force-upgrade` to ensure that any existing upgrade state gets cleared before starting the new ECE upgrade process.

raw-migrated-files/cloud/cloud-enterprise/ece_re_running_the_ece_upgrade.md

@@ -16,10 +16,8 @@ toc:
       - file: cloud-on-k8s/cloud-on-k8s/k8s-securing-stack.md
   - file: cloud/cloud-enterprise/index.md
     children:
-      - file: cloud/cloud-enterprise/ece_re_running_the_ece_upgrade.md
       - file: cloud/cloud-enterprise/ece-securing-clusters.md
       - file: cloud/cloud-enterprise/ece-securing-ece.md
-      - file: cloud/cloud-enterprise/ece-upgrade.md
   - file: cloud/cloud/index.md
     children:
       - file: cloud/cloud/ec-faq-technical.md