Update Elastic Managed integration documentation wording and links

[moxarth-rathod]

Proposed commit message

Update Elastic Managed integration documentation wording and links.

Replace the Elastic Managed documentation section in packages that support 
Elastic Managed deployments.

The previous copy described the feature as collecting data without managing Elastic Agent 
and linked to the old Serverless agentless guides. The updated text states that Elastic Managed
 integrations are supported only on Elastic Cloud Serverless and Elastic Cloud Hosted, 
that Elastic runs the collector, and it points to the current Managed integrations docs and FAQ.

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

Related issues

• Closes [Agentless] README Still Marks Agentless as Beta While Manifest has release: ga #20751

[infra-vault-gh-plugin-prod]

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

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 9 warnings, 9 suggestions found

⚠️ Warnings (9): Fix when the suggestion improves clarity or correctness.

File	Line	Rule	Message
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	50	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	50	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'that is' instead of 'i.e'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	148	Elastic.MenuArrowsBold	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	148	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	156	Elastic.MenuArrowsBold	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	156	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	187	Elastic.DontUse	Don't use 'please'. Choose a more precise or reader-focused term.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	188	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	188	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.

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

File	Line	Rule	Message
packages/tenable_sc/_dev/build/docs/README.md	26	Elastic.Wordiness	Consider using 'per' instead of 'as per'.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	26	Elastic.Versions	Use 'and later' instead of 'and newer' when referring to versions.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	90	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	100	Elastic.WordChoice	Consider using 'run, start' instead of 'execute', unless the term is in the UI.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	112	Elastic.Wordiness	Consider using 'all' instead of 'all of '.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	112	Elastic.Versions	Use 'earlier versions' instead of 'older versions' when referring to versions.
packages/ti_rapid7_threat_command/_dev/build/docs/README.md	134	Elastic.Wordiness	Consider using 'per' instead of 'as per'.
packages/ti_socradar_feeds/_dev/build/docs/README.md	32	Elastic.Semicolons	Use semicolons sparingly. Consider splitting the sentence or using a comma or conjunction.
packages/ti_socradar_taxii/_dev/build/docs/README.md	32	Elastic.Semicolons	Use semicolons sparingly. Consider splitting the sentence or using a comma or conjunction.

---

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.

[andsel]

#18627 is effectively an issue and not a PR

[andsel]

@moxarth-rathod
#18627 is the issue that's solved by #19334. So this change seems not good.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[infra-vault-gh-plugin-prod]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 9dc769f

Failed CI Steps

• Check integrations aws_securityhub
• Check integrations beyondtrust_epm
• Check integrations carbon_black_cloud
• Check integrations crowdstrike
• Check integrations github
• Check integrations imperva_cloud_waf
• Check integrations kolide
• Check integrations servicenow
• Check integrations sublime_security
• Check integrations symantec_endpoint_security
• Check integrations workday

History

• 💔 Build #48845 failed 91feb4c

cc @moxarth-rathod

[vera-review-bot]

🟢 Reviewed the latest commits 9dc769f — nothing new beyond already posted comments.

A new commit triggers another review — at most once every 15 minutes. I skip the PR while it's approved or has merge conflicts.

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

⚠️ Automated review — verify suggestions before applying.

[vera-review-bot]

@moxarth-rathod - This PR has merge conflicts with the base branch. Please resolve them.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[belimawr]

That link is from an issue, not a PR. If you follow the new link it redirects to the old one.

Suggested change

	base_image: systemd # Related issue: https://github.com/elastic/integrations/pull/10998
	base_image: systemd # Related issue: https://github.com/elastic/integrations/issues/10998