[Docs] Document SharePoint Online expand_site_group_members setting

[Jan-Kazlouski-elastic]

Documents the expand_site_group_members configuration field added to the SharePoint Online connector in elastic/connectors#4396 and exposed in Fleet via elastic/kibana#288070.

Part of elastic/chat-program#47.

Changes:

• es-connectors-sharepoint-online.md: adds expand_site_group_members to Configuration and describes compact site-group DLS behavior in Document-level security.

Docs-only change; no code or console snippets affected.

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• If submitting code, have you built your formula locally prior to submission with gradle check? (N/A — docs-only change)
• If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
• If submitting code, have you checked that your submission is for an OS and architecture that we support?

[elasticsearchmachine]

Pinging @elastic/search-extract-and-transform (Team:Search - Extract & Transform)

[github-actions]

🔍 Preview links for changed docs

• docs/reference/search-connectors/es-connectors-sharepoint-online.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[kosabogi]

LGTM with a small nit