Expose ChipIngressMaxMessageBufferBytes Telemetry config

[pkcll]

Summary

• Add [Telemetry].ChipIngressMaxMessageBufferBytes (default 1073741824 / 1 GiB) for chip-ingress batch client byte cap
• Wire through beholder client, durable emitter setup, and LOOP plugin env propagation
• Repin chainlink-common to local worktree via go.mod replace (update to merged pseudo-version before merge)

Depends on chainlink-common PR merging first.

Test plan

• go test ./core/services/chainlink/ -run TestTelemetryConfig_ChipIngressMaxMessageBufferBytes
• make config-docs
• CI green after common merge + go.mod repin

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 failed

Failed conditions
7.95% Technical Debt Ratio on New Code (required ≤ 4%)
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE