feat(embed): add TelemetrySettings provider bundle + NopTelemetry (PIPE-1066)

[Dylan-M]

Proposed Change

Adds embed.TelemetrySettings, the single bundle blitz threads from a host (or the
standalone CLI) down through module construction. Every generator, output, and the
runtime records to the providers and logger it carries. Every field is optional with a
nil-safe fallback to the process globals, so a zero-value bundle behaves as blitz did
before providers were injectable. NopTelemetry() returns a bundle wired to no-op
providers for tests and record-nothing paths.

Nothing consumes the bundle yet. Later PRs thread metrics, traces, and logs through it.

How to validate

This PR adds a type and changes no runtime behavior, so there is nothing to run yet. To
confirm it stands on its own:

• go build ./... succeeds, and a built binary behaves identically to main.
• go test ./embed/ exercises the nil-provider fallbacks and NopTelemetry.

Checklist

• Changes are tested
• CI has passed

[Dylan-M]

• fix(o11y): record output request + HEC ACK-poll latency in ms (PIPE-1404) #292
• feat(o11y): lifecycle startup-latency metrics via new runtime weaver registry (PIPE-1066) #291
• feat(o11y): bring stdout/nop outputs fully into the self-telemetry spine (PIPE-1066) #290
• feat(o11y): per-batch output send spans + HEC ACK-poll span (PIPE-1066) #289
• feat(o11y): wire fix generator into the self-telemetry spine (PIPE-1066) #288
• feat(o11y): self-logs via shared entry-point zap->OTel bridge + OTLP log export (PIPE-1066) #287
• feat(o11y): self-tracing via runtime spans, adapter emit spans, and OTLP trace export (PIPE-1066) #286
• feat(o11y): per-instance metrics via injectable MeterProvider, drop package globals (PIPE-1066) #285
• feat(embed): add TelemetrySettings provider bundle + NopTelemetry (PIPE-1066) #284 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.