Reverse Dependency: trace-dispatcher no longer depends on trace-forward

[jutaro]

This PR decouples trace-dispatcher from trace-forward, thereby removing its dependency on network-related libraries and Cardano-specific modules.

Motivation

Previously, trace-dispatcher depended on trace-forward, which in turn pulled in network and a substantial portion of the Cardano ecosystem. This entanglement made it cumbersome to use trace-dispatcher in simpler or non-Cardano settings.

What Changed

• Removed the direct dependency on trace-forward
• Refactored or restructured any modules or types that required it
• Ensured that trace-dispatcher remains focused on its core responsibility: dispatching traces, not networking

Benefits

• Lighter dependency footprint
• Easier reuse of trace-dispatcher in new projects or different ecosystems
• Paves the way for more modular and maintainable tracing infrastructure