chore: Update waku-fleet-dashboard from latest (v142) Grafana + bw per shard + req/resp req rate and traffic metrics

[NagyZoltanPeter]

Description

Noticed that our grafana dashoard (https://grafana.infra.status.im/) is diverged from our nwaku repository a lot while there is no real git/vcs friendly comparison possibility for it to decide about changes.
So while adding Bandwidth per shards, req/resp protocol request rates and traffic metrics I made a copy from grafana's v142 of fleets Nim-Waku V2

Changes

Contains all up to date changes had been made to https://grafana.infra.status.im +

Added panels:

• per shard in(gross/net) and out traffic
• store: request rate, generated in/out traffic
• filter: request rate, generated message push (out) traffic of all subs
• lightpush: request rate, inbound traffic for lightush (output appears in relay)

Removed row and panels:

• legacy filter as had been removed from nwaku for a long time.

Although these panels were already added into nwaku - repository - metrics/waku-fleet-dashboard.json it was not updated into our grafana server.

[Ivansete-status]

LGTM! Thanks for it! 💯

To understang it better, did you copy the grafana dashboard that is currently deployed in https://grafana.infra.status.im/ and then applied the changes over it?

[gabrielmer]

Thank you!

[fryorcraken]

In those graph, is it possible to display the threshold, as configured on the deployed node?

[NagyZoltanPeter]

In those graph, is it possible to display the threshold, as configured on the deployed node?

Yes I think I can add it as a separate gauge metric and show it as a dashed line.
What needs to be considered that fleet dashboards combine instances into a single panel, which can look very dense and disturbing for such amount of different values.