bump chainlink-common for chip-ingress resource attributes

[pkcll]

Summary

• Bumps chainlink-common and pkg/chipingress to the resource-attributes work in smartcontractkit/chainlink-common#2216 (which depends on smartcontractkit/chainlink-common#2267 for the ChipIngress client API).
• No chainlink application code changes required: core/cmd/shell.go already maps TOML resource attributes into beholder.Config.ResourceAttributes, and plugins/loop_registry.go already passes TelemetryAttributes to LOOP plugins.

Depends on

1. Upstream (chipingress client): Add resource attribute support to ChipIngress client chainlink-common#2267
2. Upstream (beholder wiring): Wire resource attributes into Beholder ChipIngress emitters chainlink-common#2216

Related PRs

• Related (batch config): feat: add chip-ingress batch config keys and tune defaults chainlink-common#2207

Pinned versions

• github.com/smartcontractkit/chainlink-common → v0.11.2-0.20260721063811-fccea7a53c53
• github.com/smartcontractkit/chainlink-common/pkg/chipingress → v0.0.11-0.20260721062847-690c417fc953

Known gap (from common PRs)

pkg/durableemitter is out of scope. Events emitted via durableemitter.GlobalEmit (workflows, capabilities) will not yet carry resource attributes on the cre topic. Follow-up work is tracked separately.

Test plan

• go test ./core/cmd/... ./core/services/chainlink/... ./plugins/... -short
• Manual: deploy with custom [Telemetry.ResourceAttributes], emit a platform event, verify ce_<sanitized> headers on cre

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube