[8.x] SentinelOne bidirectional processes, kill-process, and detection rule updates [ESS] (backport #5735)

[mergify]

ESS 8.16 twin of #5659. Updates the ESS docs for these features:

• [Request] Document the availability of processes response actions for SentinelOne hosts #5638
• [Request] Document the kill-process response action available for SentinelOne #5590
• [Request] Update SentinelOne bi-directional response actions instructions with new requirements for setting up the SIEM rule #5637

Previews

This is just a twin PR of content that's already been reviewed and approved, so all that's needed is codeowner approval to un-block. But if you want to confirm the AsciiDoc conversion, check these pages:

• Endpoint response actions — Revised sections for processes and kill-process to reference S1 differences.
• Third-party response actions — Added bullets to the SentinelOne tab.
• Configure third-party response actions — SentinelOne tab: Revised final step about creating detection rules.

Twin PR

• Serverless: SentinelOne bidirectional processes, kill-process, and detection rule updates [serverless] #5659

  ---

  This is an automatic backport of pull request SentinelOne bidirectional processes, kill-process, and detection rule updates [ESS] #5735 done by Mergify.

[mergify]

Cherry-pick of 9c34da7 has failed:

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

You are currently cherry-picking commit 9c34da7f.
  (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/response-actions.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.mdx

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.}