[8.14] 8.13.4 Release notes (backport #5160)

[mergify[bot]]

Fixes https://github.com/elastic/security-docs/issues/5159

Preview:

• Index page
• Release notes

  ---

  This is an automatic backport of pull request #5160 done by Mergify.

[mergify[bot]]

Cherry-pick of 0de4d61e9c3dbb4962ca7f7f3ab252e205b1985b has failed:

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

You are currently cherry-picking commit 0de4d61e.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
    both modified:   docs/release-notes.asciidoc
    both modified:   docs/release-notes/8.13.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

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[bot]]

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](https://buildkite.com/elastic/docs-build).}