[8.15] Known Issues + Access requirements for Crowdstrike Connector (backport #5848)

[mergify]

Resolves https://github.com/elastic/security-docs-internal/issues/43, updates both ESS and serverless docs.

Previews

• Stateful

  • Third-party response actions
  • Configure third-party response actions
  • Release notes 8.15 — Adds 8.15.0 known issue, and 8.15.1 release note.

• Serverless

  • Third-party response actions
  • Configure third-party response actions

    ---

    This is an automatic backport of pull request Known Issues + Access requirements for Crowdstrike Connector #5848 done by Mergify.

[mergify]

Cherry-pick of 8b7467f has failed:

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

You are currently cherry-picking commit 8b7467f9.
  (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
	modified:   docs/release-notes/8.15.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.}

[joepeeples]

run docs-build