chore(otel): bump v0.125 → v0.130 (PR-4/4, closes #225)

[trilamsr]

Summary

Final advance of the staged OTel collector pin sweep tracked by #225. With this PR the project moves from v0.125 → v0.130 and the four-PR sequence (PR-1 #243 → PR-2 #245 → PR-3 #247 → PR-4) lands the originally-requested v0.110 → v0.130 jump end-to-end.

• builder-config.yaml — every upstream + contrib gomod line bumped to v0.130.0.
• module/go.mod — collector core libs (component, consumer, processor, receiver) v1.31 → v1.36; pdata v1.31 → v1.36; per-component -test / -componenttest / -componentstatus modules v0.125 → v0.130.
• Makefile — OCB tool pin builder@v0.125.0 → builder@v0.130.0.
• docs/rfcs/0013-distro-first-pivot.md — §migration verbatim builder-config example synced to v0.130.0. Historical PR-I.1b retrospective (v0.110.0 / otel v1.30.0) intentionally left alone — that paragraph documents post-merge state at module/v0.1.0, not the current pin.

API sweep (v0.126 → v0.130)

Cross-checked the scope report against the actual code surface; no call sites needed editing this jump:

Upstream change	Sweep	Hits
v0.128 confighttp/configgrpc: TLSSetting → TLS	grep -rn 'TLSSetting' --include='*.go' --include='*.yaml' .	0
v0.128 pipeline.MustNewID[WithName] removed	grep -rn 'pipeline.MustNewID' --include='*.go' .	0
v0.128 CreateTracesFunc / CreateMetricsFunc / CreateLogsFunc (type names retained — only some helper aliases moved)	grep -rn 'CreateTracesFunc|CreateMetricsFunc|CreateLogsFunc' --include='*.go' .	doc-comment refs only; resolved types still exist
v0.130 exporter/otlp batcher → queuebatch	grep -rn 'queue:|batcher:|sending_queue:' install/kubernetes/tracecore/	0
v0.130 configgrpc/confighttp configoptional.Optional	indirect; surfaces only if we pin those configs in chart values	0 chart-side hits

The pivot's minimum recipe surface (otlp · filelog · journald · prometheus · k8sobjects · hostmetrics · transform · filter · k8sattributes · batch · otlphttp · debug · datadog · clickhouse · filestorage · healthcheck · zpages) never touched the deprecated knobs, so the v0.128 / v0.130 renames stay invisible to operators on the binding recipes.

Verification

GOWORK=off go build ./...     # root  — clean
GOWORK=off go build ./...     # module — clean
GOWORK=off go test  ./...     # root  — all packages pass
GOWORK=off go test  ./...     # module — all packages pass
make build                    # OCB end-to-end @ builder@v0.130.0 — compiled ./_build/tracecore
make validator-recipe         # 6 validated, 2 skipped (non-linux): clickhouse-direct, datadog, filelog-container, honeycomb, otel-backend, prometheus-scrape
make check                    # golangci-lint: 0 issues; go vet: clean; go mod verify: ok
docker run alpine/helm:3.16.4 lint install/kubernetes/tracecore  # 1 chart linted, 0 failed

All four pivot recipes that touched contrib (datadog, prometheus-scrape, clickhouse-direct, otel-backend) validate against the freshly-built collector — no operator-facing field renames slipped in.

Self-grade

A+. Scope target hit (final pin advance + RFC sync), every binding verification gate is green on the actual diff, zero API workarounds (root cause: no call sites use the renamed surfaces in this jump), no scope creep beyond the bump itself, and the staged-sweep PR-1/2/3/4 sequence lands #225 exactly as RFC-scoped.

Release notes

- chore(otel): bump pinned OpenTelemetry Collector + contrib + OCB builder from v0.125 to v0.130 across builder-config.yaml, module/go.mod (pdata v1.36, core libs v1.36), and the Makefile OCB pin. Closes the v0.110 → v0.130 staged sweep (PR-4 of 4).
- docs(rfc): sync the RFC-0013 verbatim builder-config example block to v0.130.0.

Closes #225 (PR-4/4 of the staged sweep).

Refs: #243 (PR-1), #245 (PR-2), #247 (PR-3).