crowdstrike: remove incorrect no-limit max_executions documentation

[efd6]

Proposed commit message

crowdstrike: remove incorrect no-limit max_executions documentation

In the alert, host, indentity_protection_assessment,
indentity_protection_timeline and vulnerability, the number of CEL
executions allowed for each periodic evaluation can be configured. The
documentation in the user interface says that this limit can be lifted
if it is set to zero. This is not the case, by design. So remove the
statement.

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

• Fixes [CrowdStrike]: Setting max_executions to 0 for unlimited fails #19762

Screenshots

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 5 suggestions found

💡 Suggestions (5): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
packages/crowdstrike/data_stream/alert/manifest.yml	62	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/crowdstrike/data_stream/host/manifest.yml	78	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/crowdstrike/data_stream/identity_protection_assessment/manifest.yml	55	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/crowdstrike/data_stream/identity_protection_timeline/manifest.yml	61	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/crowdstrike/data_stream/vulnerability/manifest.yml	73	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.

---

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]

✅ All changelog entries have the correct PR link.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: a1f4023

cc @efd6

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[vera-review-bot]

👀 I have started reviewing the PR

[vera-review-bot]

Vera Review Bot

For the current commit state, I did not find any issues.

---

🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills

⚠️ Automated review — verify suggestions before applying.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[elastic-vault-github-plugin-prod]

Package crowdstrike - 3.26.1 containing this change is available at https://epr.elastic.co/package/crowdstrike/3.26.1/