[Request][7.17] Doc privs required to create and manage the .lists data stream (backport #4696)

[mergify]

This is an automatic backport of pull request #4696 done by Mergify.
Cherry-pick of 2990160 has failed:

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

You are currently cherry-picking commit 2990160.
  (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/detections/api/exceptions/exceptions-api-overview.asciidoc
	modified:   docs/detections/api/exceptions/lists-index-api-overview.asciidoc
	modified:   docs/detections/api/lists/lists-api-overview.asciidoc

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/getting-started/detections-req.asciidoc

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

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[github-actions]

A documentation preview will be available soon.

Help us out by validating the Buildkite preview and reporting issues here.
Please also be sure to double check all images to ensure they are correct in the preview.

• 🔨 Buildkite builds
• 📚 HTML diff: Buildkite - Jenkins
• 📙 Preview: Buildkite - Jenkins
• 🧪 Buildkite vs Jenkins diff

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