Create Waku diagnostic tool

[felicio]

What

• Test
  • The difference in perf. between the fleets/networks that are bridged to waku v1 and the fleets/networks that are not and
  • The differences in perf. between the nim-waku fleets and go-waku fleets
  • Spec source https://discord.com/channels/624205794384281629/1014557341926043769/1015208208249409586

[felicio]

My notes:

• for protocol type
  • fetching / store
  • observing / relay
• ops
  • type
    • connecting
    • en/decoding
    • waiting
  • fields
    • start time / crated at
    • end time / received at
• query params
  • topic
  • direction
  • size
  • start time
  • end time
• request fields
  • fleet
  • node/peer address
• response fields
  • message id(s)
  • message count
  • call count
• test fields
  • start time
  • end time
  • elapsed time
• message type
  • community
  • chat message
• misc.
  • earch record/test run per line
• kibana link
• grafana link
• versions / commit
  • js-waku
  • status-web
  • nim-waku
  • go-waku
• ?from diff locations (e.g. us, eu)

---

• ?run test periodically in a headless browser deployed to a server and send results to elastic

[felicio]

Relates to https://github.com/status-im/nwaku/issues/1160