Add group field to nginx packages

[teresaromero]

Proposed commit message

Add group: nginx to the manifest of all nginx-related packages: nginx, nginx_ingress_controller, nginx_ingress_controller_otel, nginx_otel, nginx_input_otel.

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

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

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

{
  "name": "nginx",
  "version": "3.2.2",
  "type": "integration",
  "group": "nginx"
}

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: b3afe03

History

• 💔 Build #47247 failed 4924162

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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

[elastic-vault-github-plugin-prod]

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