Add group field to kafka packages

[teresaromero]

Proposed commit message

Add group: kafka to the manifest of all kafka-related packages: kafka, kafka_connect, kafka_input_otel, kafka_log, kafka_otel.

WHAT: Adds a group field to each package's manifest.yml, immediately after the type field, with the value kafka. Each package receives a patch version bump and a corresponding changelog entry.

WHY: The Kibana UI uses the group field to display related packages as a unified technology tile, allowing users to discover and install the full kafka observability stack from a single entry point.

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

• Verify group: kafka appears in all 5 package manifests.
• Verify the Kibana UI renders the kafka technology tile correctly grouping all packages.

How to test this PR locally

Start a local registry (v1.40.0) pointing at this branch using elastic-package v0.126.0 and query each package:

elastic-package stack up

Requires elastic-package v0.126.0, which starts the registry at v1.40.0.

GET https://localhost:8080/search?package=kafka
GET https://localhost:8080/search?package=kafka_connect
GET https://localhost:8080/search?package=kafka_input_otel
GET https://localhost:8080/search?package=kafka_log
GET https://localhost:8080/search?package=kafka_otel

Each response should contain "group": "kafka". Example:

GET https://localhost:8080/search?package=kafka

{
  "name": "kafka",
  "version": "1.27.2",
  "type": "integration",
  "group": "kafka"
}

Related issues

• Relates https://github.com/elastic/ingest-dev/issues/8085

Screenshots

[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.

[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: d3df89c

History

• 💔 Build #47253 failed 9c44eec

[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 kafka - 1.27.2 containing this change is available at https://epr.elastic.co/package/kafka/1.27.2/

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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