bump chainlink-common for chip-ingress resource attributes

[pkcll]

Summary

• Bumps chainlink-common and pkg/chipingress to smartcontractkit/chainlink-common#2216, which propagates [Telemetry.ResourceAttributes] to the ChipIngress cre topic via gRPC metadata headers and CloudEvent extensions.
• No chainlink 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

• Add resource attribute support to ChipIngress client chainlink-common#2216

Known gap (from common PR)

pkg/durableemitter is out of scope in chainlink-common#2216. 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

Made with Cursor

[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

[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