loop: pass beholder TracerProvider to the durable emitter

[pkcll]

Summary

• Passes the TracerProvider of the beholder client to durableemitter.Setup in the LOOP server, alongside the existing Meter, so the plugin-side durable emitter and its chip ingress client use the tracer provider of beholder.
• Addresses the Copilot review comment on durableemitter: add tracing spans and chip ingress client name #2432: the retransmit deliver test now waits for the tick span that queued the row to end, then asserts the deliver span parent, link and trace ID against that tick (previously it only compared the link to the parent, and looked the tick up immediately, which could race with the delivery callback).
• Bumps pkg/chipingress in go.mod to the latest main pseudo-version v0.0.11-0.20261005132539-b7d63d5fd549 (commit b7d63d5). No release tag is needed.

PR stack

1. chipingress: add WithClientName option #2433 - chipingress: add WithClientName option (merged)
2. durableemitter: add tracing spans and chip ingress client name #2432 - durableemitter: add tracing spans and chip ingress client name (merged)
3. loop: pass beholder TracerProvider to the durable emitter #2434 - loop: pass beholder TracerProvider to the durable emitter (this PR) (base: main)

Jira: INFOPLAT-19423

Notes

• When no telemetry endpoint is set, beholder.GetClient() is the noop client, so its tracer provider is a noop. Durable emitter spans are then off even if tracing is enabled via SetupTracing (same as Meter today).
• bc.TracerProvider is not wrapped by the pyroscope tracer provider, so these spans are not linked to profiles when PyroscopeLinkTracesToProfiles is on.

Test plan

• go build ./pkg/..., go vet, go mod tidy -diff clean
• go test -race ./pkg/durableemitter/ ./pkg/loop/; the retransmit link test passes 80 runs under -race
• CI

[github-actions]

📊 API Diff Results

No changes detected for module github.com/smartcontractkit/chainlink-common

View full report

[Copilot]

Copilot review overview

🟢 Approval recommended

The provider behavior matches the documented intent, and no blocking issues remain.

Review effort: Balanced
Findings: None

What changed in this PR

Routes LOOP durable-emitter tracing through Beholder’s provider, completing the tracing integration.

Changes:

• Passes Beholder’s tracer provider to durable-emitter setup.
• Waits for the parent retransmit tick before checking span relationships.
• Updates the chipingress dependency and checksums.

File	Description
pkg/​loop/​server.go	Supplies Beholder’s tracer provider.
pkg/​durableemitter/​tracing_test.go	Synchronizes and strengthens span assertions.
go.sum	Updates chipingress checksums.
go.mod	Advances the chipingress pseudo-version.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.