[9.3](backport #51862) Docs: Update applies_to version for Kafka input settings

[mergify]

Updated the applies_to versions for timeout, keep_alive, session_timeout, and heartbeat_interval settings (added in #51173) in the Kafka input documentation as these settings were backported to 9.4 (#51769) and 9.3 (#51770).

Docs

Proposed commit message

This PR updates the applies_to version for timeout, keep_alive, session_timeout, and heartbeat_interval settings in the Kafka input documentation as these settings were backported to 9.3.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

---

This is an automatic backport of pull request #51862 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of d884560 has failed:

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

You are currently cherry-picking commit d88456082.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/reference/filebeat/filebeat-input-kafka.md

no changes added to commit (use "git add" and/or "git commit -a")

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

[botelastic]

This pull request doesn't have a Team:<team> label.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[github-actions]

TL;DR

The pre-commit job failed because check-merge-conflict found unresolved Git conflict markers in docs/reference/filebeat/filebeat-input-kafka.md. Resolve the backport conflict, commit the corrected file, and rerun the workflow.

Remediation

• Resolve the four conflict blocks in docs/reference/filebeat/filebeat-input-kafka.md at lines 101-105, 113-117, 125-129, and 137-141, preserving the intended Kafka documentation and applies_to updates.
• Commit/push the resolved backport branch, then rerun the pre-commit workflow and confirm the check-merge-conflict hook passes.

Investigation details

Root Cause

The workflow run failed in Run elastic/oblt-actions/pre-commit@v1, specifically the check-merge-conflict hook. The PR already has an unresolved cherry-pick conflict in this same file.

Evidence

• Workflow: https://github.com/elastic/beats/actions/runs/29322424523
• Job/step: pre-commit / Run elastic/oblt-actions/pre-commit@v1
• Key log excerpt: check for merge conflicts ... Failed; docs/reference/filebeat/filebeat-input-kafka.md:101: Merge conflict string u003cu003cu003cu003cu003cu003cu003c found, with additional markers at lines 103, 105, 113, 115, 117, 125, 127, 129, 137, 139, and 141; the process exited with code 1.

Validation

• No local tests were run; this is a documentation conflict-marker failure detected directly by the workflow hook.

Follow-up

• After resolving the conflict, rerun the failed workflow and verify the generated documentation remains consistent with the backported Kafka input changes.

---

What is this? | From workflow: PR Actions Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.