[8.x] [8.18][Serverless] Alert status information re-added to flyout (backport #6415)

[mergify]

Fixes #6382 by re-adding the docs for the alert status change field in the alert details flyout. The associated screenshot has also been refreshed.

Previews:

• ESS - https://security-docs_bk_6415.docs-preview.app.elstc.co/guide/en/security/master/view-alert-details.html#about-section
• Severless - https://security-docs_bk_6415.docs-preview.app.elstc.co/guide/en/serverless/main/security-view-alert-details.html#about-section

  ---

  This is an automatic backport of pull request [8.18][Serverless] Alert status information re-added to flyout  #6415 done by Mergify.

[mergify]

Cherry-pick of 32cecfd has failed:

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

You are currently cherry-picking commit 32cecfdd.
  (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/alerts-view-details.asciidoc
	modified:   docs/detections/images/about-section-rp.png

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/alerts/view-alert-details.asciidoc
	deleted by us:   docs/serverless/images/view-alert-details/-detections-about-section-rp.png

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

[nastasha-solomon]

run docs-build