build(deps): bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.18.0 to 0.20.0

[dependabot]

Bumps github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.18.0 to 0.20.0.

Changelog

Sourced from github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor's changelog.

Releasing opentelemetry-collector-components

Optional steps

Normally the following steps are not required for releasing the components. The update of otel based on upstream is automated and should not be performed manually unless there are specific reasons for this.

1. (optional) Open a PR to the repository to use the newly released OpenTelemetry Collector Core version by doing the following:
   • Ensure your local repository is up-to-date with upstream and create a new Git branch named release/<release-series> (e.g. release/v0.85.x)
   • Manually update core and contrib collector module versions in ../distributions/elastic-components/manifest.yaml
   • Manually update the version to be released in the versions.yaml file
   • Run make genelasticcol
   • Commit the changes
   • Run make update-otel OTEL_VERSION=vX.Y.Z OTEL_STABLE_VERSION=vA.B.C
     • If there is no new stable version released in the core collector, use the current stable module version in contrib as OTEL_STABLE_VERSION.
   • If you were unable to run make update-otel before releasing core, fix any errors from breaking changes.
   • Commit the changes
   • Open the PR 🛑 Do not move forward until this PR is merged. 🛑

Create the new tags

2. Bump up the module-sets.edit-base.version in versions.yaml i.e. from v0.20.0 to v0.21.0

   🛑 Cross check latest version used by EDOT and https://github.com/elastic/opentelemetry-collector-components/tags 🛑

3. Tag the module groups with the new release version by running:

   ⚠️ If you set your remote using https, you need to include REMOTE=https://github.com/elastic/opentelemetry-collector-components.git in each command. ⚠️

   • Run make push-tags.

   If you encounter an error when running make push-tags like:

   Load key "~/.ssh/id_ed25519": incorrect passphrase supplied to decrypt private key error: unable to sign the tag
   

   It’s likely because Git is trying to sign a tag using an SSH key that requires a passphrase.

   ✅ Solution: Run the following commands to decrypt your SSH key and make it available for Git tag signing:

   eval "$(ssh-agent -s)"
   ssh-add <YOUR_SSH/GPG_KEY_PATH>
   make push-tags

... (truncated)

Commits

• a5abfab chore(deps): bump github.com/elastic/opentelemetry-lib (#855)
• 764ee5b chore(deps): bump github.com/elastic/opentelemetry-lib (#858)
• 602a655 chore(deps): bump the otel-dependencies group across 20 directories with 49 u...
• 7ed710e Allow dynamic limiter to scale ingest rate below static limit (#851)
• 0cb3e9a chore(deps): bump github.com/elastic/opentelemetry-lib (#857)
• b7bdeec chore(deps): bump github.com/elastic/opentelemetry-lib (#856)
• a673657 chore(deps): bump github.com/elastic/opentelemetry-lib (#854)
• 90375f4 chore(deps): bump github.com/elastic/apm-data (#840)
• 179647f chore(deps): bump elastic/oblt-actions from 1.33.5 to 1.33.6 (#853)
• b21c7a4 [receiver/elasticapmintake] Fix APM error http semconv translations (#849)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[github-actions]

@Mergifyio backport 8.19 9.0 9.1 9.2

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: a5a77e5

Failed CI Steps

• Unit tests - Windows 2022
• x86_64:sudo: default
• x86_64:sudo: fleet
• x86_64:sudo: fleet

[mergify]

backport 8.19 9.0 9.1 9.2

✅ Backports have been created

• #10832 [8.19] (backport #10829) build(deps): bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.18.0 to 0.20.0 has been created for branch 8.19 but encountered conflicts
• #10833 [9.0] (backport #10829) build(deps): bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.18.0 to 0.20.0 has been created for branch 9.0 but encountered conflicts
• #10834 [9.1] (backport #10829) build(deps): bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.18.0 to 0.20.0 has been created for branch 9.1 but encountered conflicts
• #10835 [9.2] (backport #10829) build(deps): bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.18.0 to 0.20.0 has been created for branch 9.2 but encountered conflicts