[microsoft_sqlserver] upgrade to 2025 version

[giorgi-imerlishvili-elastic]

Proposed commit message

Add SQL Server 2022 and 2025 support.
availability_groups: collect per-replica state from sys.dm_hadr_availability_replica_states;
add is_contained (SQL 2022+), basic_availability_group (SQL 2016–2022, removed in SQL Server 2025),
and is_distributed (SQL 2016+) fields via sys.columns-guarded dynamic SQL so all three columns
return NULL instead of an error when absent on the running SQL Server version.
audit: add obo_middle_tier_app_id, obo_middle_tier_app_name, external_policy_permissions_checked fields (SQL 2022+);
add LEDGER_OPERATION_GROUP, EXTERNAL_POLICY_OPERATION_GROUP (SQL 2022), VECTOR_OPERATION_GROUP, and
EXTERNAL_REST_ENDPOINT_GROUP (SQL 2025) audit action group mappings.
performance: add external_rest_endpoint_total_executions counter via SQLServer:External REST Endpoint (SQL 2025+).
transaction_log: add ADR Persistent Version Store (PVS) metrics from
sys.dm_tran_persistent_version_store_stats (SQL 2022+) via version-safe dynamic SQL.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes https://github.com/elastic/obs-integration-team/issues/972

Screenshots

[github-actions]

Vale Linting Results

Summary: 4 warnings, 7 suggestions found

⚠️ Warnings (4)

File	Line	Rule	Message
packages/microsoft_sqlserver/_dev/build/docs/README.md	52	Elastic.DontUse	Don't use 'Please'.
packages/microsoft_sqlserver/docs/README.md	52	Elastic.DontUse	Don't use 'Please'.
packages/microsoft_sqlserver/docs/README.md	247	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/microsoft_sqlserver/docs/README.md	248	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.

💡 Suggestions (7)

File	Line	Rule	Message
packages/microsoft_sqlserver/_dev/build/docs/README.md	158	Elastic.Wordiness	Consider using 'because' instead of 'since'.
packages/microsoft_sqlserver/docs/README.md	158	Elastic.Wordiness	Consider using 'because' instead of 'since'.
packages/microsoft_sqlserver/docs/README.md	556	Elastic.Wordiness	Consider using 'because' instead of 'since'.
packages/microsoft_sqlserver/docs/README.md	685	Elastic.Wordiness	Consider using 'because' instead of 'since'.
packages/microsoft_sqlserver/docs/README.md	686	Elastic.Wordiness	Consider using 'because' instead of 'since'.
packages/microsoft_sqlserver/docs/README.md	687	Elastic.Wordiness	Consider using 'because' instead of 'since'.
packages/microsoft_sqlserver/docs/README.md	689	Elastic.Wordiness	Consider using 'because' instead of 'since'.

---

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.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 63acc4d

History

• 💚 Build #40995 succeeded 7ed1e70

cc @giorgi-imerlishvili-elastic