Add group field to prometheus packages

[teresaromero]

Proposed commit message

Add group: prometheus to the manifest of all prometheus-related packages: prometheus, prometheus_input, prometheus_input_otel, prometheus_input_otel_raw.

WHAT: Adds a group field to each package's manifest.yml, immediately after the type field, with the value prometheus. 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 prometheus 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: prometheus appears in all 4 package manifests.
• Verify the Kibana UI renders the prometheus 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=prometheus
GET https://localhost:8080/search?package=prometheus_input
GET https://localhost:8080/search?package=prometheus_input_otel
GET https://localhost:8080/search?package=prometheus_input_otel_raw

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

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

{
  "name": "prometheus",
  "version": "1.24.4",
  "type": "integration",
  "group": "prometheus"
}

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.

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 0e154cb

History

• 💔 Build #47249 failed 7161295

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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