epic: expose transport metrics

[SgtPooki]

Done Criteria

1. Export metrics leveraging the work done in C. 🔮 Ergonomic Observability #1458
2. Transport metrics, similar to those already created for TCP, are emitted for all js-libp2p transports

Motivation

Epic created since we only had one tracking the work from #1915

Better observability for performance and benchmarking. See: #1458 (comment)

Questions

• Do we want to add metrics to packages/transport-circuit-relay-v2?

Related

• feat: Expose Metrics for Websockets #1915
• feat: add WebSockets metrics #2649 (comment)
• docs(metrics): update metrics.md  #2077
• docs(readme): link to metrics-prometheus API docs #2080
• docs: include metrics-prometheus API docs link in readme #2099

Tasks

Beta Give feedback

1. feat: Expose Metrics for Websockets #1915
   exp/intermediate kind/enhancement +2
   
2. feat: expose metrics for WebTransport
3. feat: expose metrics for WebRTC
4. feat: expose metrics for maconn upgrades in @libp2p/upgrader (part of libp2p npm package: https://github.com/libp2p/js-libp2p/blob/7939dbd5cbab1c7b4be671ff976d0258e9b48178/packages/libp2p/src/upgrader.ts#L126C36-L126C52)