[8.15] Document how to troubleshoot Defend's self-healing feature on Windows (backport #6361)

[mergify]

Resolves #2830 by adding a new troubleshooting section on disabling Elastic Defend's self-healing feature.

Previews

ESS: Elastic Defend

Serverless: Elastic Defend

---

This is an automatic backport of pull request #6361 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of c4db057 has failed:

On branch mergify/bp/8.15/pr-6361
Your branch is up to date with 'origin/8.15'.

You are currently cherry-picking commit c4db057f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/troubleshooting/ts-management.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/troubleshooting/troubleshoot-endpoints.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}