[8.x] [Jan 28] MS Defender for Endpoint third-party response integration (backport #6478)

[mergify]

Resolves #6303.

Previews

ESS:

• Third-party response actions: Added new section for Microsoft Defender for Endpoint response actions
• Configure third-party response actions: Added new expandable section for setting up Microsoft Defender for Endpoint response actions

Serverless:

• Third-party response actions: Added new tab for Microsoft Defender for Endpoint response actions
• Configure third-party response actions: Added new tab for setting up Microsoft Defender for Endpoint response actions

  ---

  This is an automatic backport of pull request [Jan 28] MS Defender for Endpoint third-party response integration #6478 done by Mergify.

[mergify]

Cherry-pick of 9148adb has failed:

On branch mergify/bp/8.x/pr-6478
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 9148adbb.
  (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/management/admin/response-actions-config.asciidoc
	modified:   docs/management/admin/third-party-actions.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/endpoint-response-actions/response-actions-config.asciidoc
	deleted by us:   docs/serverless/endpoint-response-actions/third-party-actions.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.}