[8.15] Antivirus registration enabled by default (backport #5494)

[mergify]

Resolves #5472 — updates both classic & serverless docs.

Previews

Classic:

• Configure an integration policy for Elastic Defend | Register Elastic Security as antivirus (optional)

Serverless:

• Click the link below, then in the Security card click View serverless docs.
• Navigate to: Secure your endpoints → Configure an integration policy | Register Elastic Security as antivirus (optional)

  ---

  This is an automatic backport of pull request Antivirus registration enabled by default #5494 done by Mergify.

[mergify]

Cherry-pick of a154eeb has failed:

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

You are currently cherry-picking commit a154eeb1.
  (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/getting-started/configure-integration-policy.asciidoc
	modified:   docs/getting-started/images/register-as-antivirus.png

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/edr-install-config/configure-endpoint-integration-policy.mdx
	deleted by us:   docs/serverless/images/configure-endpoint-integration-policy/-getting-started-register-as-antivirus.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.}

[joepeeples]

run docs-build