opentelemetry-collector: bump chart to v0.131.1 and lock ebpfProfiler default image tag

[povilasv]

Motivation

• Bump the Helm chart and collector app version to pick up new collector releases and record the changes in the changelog.
• Ensure the ebpfProfiler preset uses a specific, known-safe image tag by default while still allowing user overrides via image.tag.

Description

• Updated Chart.yaml to version: 0.131.1 and appVersion: 0.151.0.
• Added v0.131.1 and v0.131.0 entries to CHANGELOG.md noting the ebpfProfiler image tag behavior and the app bump.
• Modified templates/_custom_helpers.tpl in the opentelemetry-collector.image helper to set the default $imageTag to "0.147.0" when .Values.presets.ebpfProfiler.enabled, while keeping the existing repository selection logic and allowing image.tag and image.digest to override.

Testing

• Ran helm lint against the chart and it succeeded.
• Rendered templates with helm template for an installation with .Values.presets.ebpfProfiler.enabled = true and verified the image tag defaults to 0.147.0.
• Rendered templates with an explicit image.tag override and verified the override was applied successfully.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a56cf161b9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Regenerate rendered examples after appVersion bump

Bumping appVersion to 0.151.0 without updating charts/opentelemetry-collector/examples/**/rendered leaves the checked-in manifests on the old 0.147.0 image, so CI paths that apply rendered examples are no longer validating the version shipped by this chart change. I verified this by checking .github/workflows/collector-test.yaml and .github/workflows/ebpf-test.yaml, which run kubectl apply -f ./charts/opentelemetry-collector/examples/daemonset-and-deployment/rendered, while that rendered manifest still references opentelemetry-collector-contrib:0.147.0.

Useful? React with 👍 / 👎.