chore(internal telemetry): Enable pedantic Clippy lints

[pront]

Summary

Enable pedantic Clippy checks for internal allocation telemetry. Replace manual panic branches with assertions, shorten private metadata field names, and document panic conditions. Retain narrow, issue-linked allowances for hot-path inlining, signed byte accounting, and the paired token API.

References

Related: #23659. Split from #26574.

Vector configuration

The allocation-tracing smoke pipeline used demo_logs -> blackhole and internal_metrics -> console, with --allocation-tracing --allocation-tracing-reporting-interval-ms 100.

How did you test this PR?

• make fmt and git diff --check passed.
• Workspace/all-target Clippy passed with sinks-blackhole,sinks-console,sources-demo_logs,sources-internal_metrics,tikv-jemallocator.
• All 23 selected tracing, internal-metrics, demo-log, and blackhole regression tests passed with the same features.

The allocation-tracing smoke run aborts in AllocationGroupId::from_raw because NonZeroU8::new_unchecked receives zero. The identical failure reproduced on unchanged base 7477209c805bb9cdaa7547d95fd66e650be69423; end-to-end allocation tracing remains unvalidated. The patch was restored byte-for-byte after the comparison.

Does this PR include user facing changes?

• Yes.
• No.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-09T14:03:29.780427Z	6174b32	PR opened
🔒 Security Review	✅ Completed 2026-10-09T14:04:29.730094Z	6174b32	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadoghq-integration]

More details

The assertion rewrites preserve existing stack failure conditions, and the metadata renames preserve emitted metric labels. End-to-end allocation tracing remains unvalidated because the PR reports the same abort on the base commit.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 6174b32}