fix(security): inherit component_type on confinement gauge from ambient span

[vladimir-dd]

Summary

ConfinementConfig::set_confinement_gauge explicitly hardcoded component_type/component_kind labels from the calling sink's own Self::NAME. This is the only per-component metric in Vector that does this — every other one (e.g. component_sent_events_total, http_client_requests_sent_total) inherits component_type from the ambient tracing span the topology builder opens around the whole SinkConfig::build call (component_type = %sink.inner.get_component_name() in src/topology/builder.rs).

That's harmless when a sink is built directly, since Self::NAME matches the ambient span's type anyway. But it breaks when:

• One sink delegates its build to another SinkConfig::build internally (e.g. humio_metrics → humio_logs), or
• An external/downstream sink constructs a Vector sink config and calls .build() on it directly to wrap it.

In both cases the gauge reports the delegate's own component type instead of the wrapping sink's — while every other metric on that same build correctly reports the wrapping sink's type, because they don't override the ambient span.

Fix

Drop the explicit component_kind/component_type parameters from set_confinement_gauge entirely and let it inherit from the ambient span like every other metric. Updated all 27 call sites across the sink modules accordingly. No behavior change for sinks built directly; delegating/wrapping sinks now report the correct component type with no extra plumbing.

An earlier version of this fix instead widened HumioLogsConfig::build_without_confinement_gauge's visibility so external wrappers could pass their own component name explicitly — that would have worked for this one case but wouldn't have fixed the general inconsistency (any future delegating/wrapping sink would hit the same bug), so this PR fixes the actual root cause instead.

Vector configuration

N/A — this only changes internal metric tagging, not sink behavior or configuration surface.

How did you test this PR?

• cargo check -p vector --lib --no-default-features --features sinks — clean, no errors/warnings.
• cargo clippy -p vector --lib --no-default-features --features sinks --no-deps — clean.
• cargo test -p vector --lib --no-default-features --features sinks template:: — 42 passed, 0 failed.
• cargo fmt

Change Type

• Bug fix
• New feature
• Dependencies
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Changelog fragment added at changelog.d/confinement_gauge_component_type_override.fix.md.
• No.

References