feat: expose code metrics

[weboko]

Description

Following example of js-libp2p we should consider exposing internal behavior of js-waku through a set of packages and API in order to allow application developers to track and measure behavior of it.

On top we should investigate if we can provide some simple pre-setup boards that can visualize captured metrics.

With this sub-task we should be cautious and facilitate needs only relevant for Browser environment. From that PoV some things might not be needed.

User Story

• As a consumer, I want to see past performance of the node by uploading logs to a visualizer.
• As a consumer, I want to measure performance of the node in run time and report to a server if needed.

Proposed Solution / Feature Design

Expose internal metrics through new API and potentially new packages.

Notes

Refer to the main feature task for details.

[weboko]

This task has low priority and should be approached only when we see the need of more structural telemetry / metrics capturing OR/AND if we see it useful to provide some visualization to logs/metrics in order to speed up debugging and investigations.