feat: init fuel-telemetry

[kayagokalp]

Re-enabling tracing, it was problematic in the past because of how we integrated this. Little bit more details:

The WorkerGuard from fuel-telemetry was stored in a static OnceLock in forc-tracing, preventing its Drop implementation from running. This caused, zombie processes remaining after CLI tool execution

Refactored init_tracing_subscriber() to return the WorkerGuard to the caller, enabling proper RAII cleanup when programs exit.

[github-actions]

LCOV of commit 9a50d32 during CI #64

Summary coverage rate:
  lines......: 44.2% (1249 of 2823 lines)
  functions..: 34.0% (158 of 465 functions)
  branches...: 28.4% (63 of 222 branches)

Files changed coverage rate: n/a

[cursor]

PR Summary

Introduces telemetry across forc CLI tools and updates tracing initialization.

• Adds fuel-telemetry integration in forc-tracing (v0.72.0) with optional telemetry feature enabled by default; re-exports telemetry macros and hides telemetry spans from regular logs
• Refactors init_tracing_subscriber(...) to return Result<Option<WorkerGuard>>; callers (forc-crypto, forc-wallet, forc-node) now hold and drop the guard to ensure proper shutdown
• Extends tracing options (disable via env/option, new Stdout writer mode, adjusted log-level application, regex filtering) and updates CHANGELOG
• Bumps workspace to forc-tracing = 0.72.0 and adds fuel-telemetry dependency; lockfile updates for new/updated crates

^{Written by Cursor Bugbot for commit 9a50d32. This will update automatically on new commits. Configure here.}

[JoshuaBatty]

might as well update the changelog for forc-tracing at the same time

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Telemetry stub macros are dead code due to conflicting cfg guards

Medium Severity

The telemetry module is declared with #[cfg(feature = "telemetry")] in lib.rs, meaning telemetry.rs is only loaded when telemetry is enabled. However, the stub macros inside telemetry.rs are gated with #[cfg(not(feature = "telemetry"))]. These conditions are mutually exclusive, so the disabled_telemetry module and its stub macros can never be compiled. When users disable telemetry and attempt to use these macros, they'll get a confusing "module not found" error instead of the intended clear error message about enabling the telemetry feature.

Additional Locations (1)

• forc-tracing/src/lib.rs#L2-L4