fix(monitor): store counter on wallet account

[SantiagoPittella]

Summary

After running a benchmarks against devnet I noticed something off in the network monitor's counter: it was being properly increased by with a constant difference between the expected and the actual value of 7.

This was weird because usually it should catch up or not increase at all, and the cards was stuck as unhealthy (at the time of opening the PR it is still marked as unhealthy). We have some mechanisms to fix counter issues on runtime but, after some time debugging, I realized what happened:

• I was running benchmarks
• The monitor was increasing the counter too.
• The mempool was at its limits.
• Some monitor txs were rejected because of the mempool being full (this case is handled in the monitor).
• Some monitor txs were acked and accepted by the node, but then the mempool dropped the transactions/were reverted (the case not handled in the monitor).
• After the benchmark the network's load was reduced and everything started to run smoothly from there, making the counter to keep being increased.

To avoid this for happening in the future, this PR adds a counter in the wallet's storage as a new slot. This way we ensure that if the tx succeeds the counter is increased and the network note was truly created.

Changelog

[[entry]]
scope       = "network-monitor"
impact      = "fixed"
description = "Reverted transactions no longer desync counter state"

[Mirko-von-Leipzig]

Ah yeah I'd seen that before a few times back when testnet crash looped.

Nice fix!