[8.x] [Jan 28] GA for third-party response actions (backport #6471) (#6489)

* GA for third-party response actions (#6471)

(cherry picked from commit 285d9d3)

# Conflicts:
#	docs/serverless/endpoint-response-actions/response-actions-config.asciidoc
#	docs/serverless/endpoint-response-actions/third-party-actions.asciidoc

* Delete docs/serverless directory and its contents

---------

Co-authored-by: natasha-moore-elastic <[email protected]>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: 3 people

docs/management/admin/response-actions-config.asciidoc

@@ -6,8 +6,6 @@
 :frontmatter-tags-content-type: [how-to]
 :frontmatter-tags-user-goals: [manage]
 
-preview::[]
-
 You can direct third-party endpoint protection systems to perform response actions on enrolled hosts, such as isolating a suspicious endpoint from your network, without leaving the {elastic-sec} UI. This page explains the configuration steps needed to enable response actions for these third-party systems:
 
 * CrowdStrike

docs/management/admin/third-party-actions.asciidoc

@@ -6,8 +6,6 @@
 :frontmatter-tags-content-type: [reference]
 :frontmatter-tags-user-goals: [manage]
 
-preview::[]
-
 You can perform response actions on hosts enrolled in other third-party endpoint protection systems, such as CrowdStrike or SentinelOne. For example, you can direct the other system to isolate a suspicious endpoint from your network, without leaving the {elastic-sec} UI.
 
 .Requirements