Add nwaku into status-go

[Ivansete-status]

Summary

https://github.com/status-im/status-go should operate with waku through nwaku

We need to add a new nwaku submodule within status-go and adapt the current status-go code base plus nwaku-libwaku so that we can have status-go working with nwaku.

There will be changes in:

• status-go to integrate nwaku
• nwaku to extend libwaku with the features needed by status-go

Tasks

• chore: update to nim 2.0 status-im/status-desktop#16472

The following tasks must be reviewed since it's possible some of these are already implemented in nwaku

• New
  • Merge Config and WakuConfig
  • Expose bandwidth counters from nwaku and integrate with telemetry
  • feat: expose a topic health status channel in nwaku #3196
  • feat(libwaku): enable filter/lightpush/px and setup rate limits status-im/status-go#6223
  • feat(libwaku): add protected shard #3211
• Check for connection changes
  • Expose a connections channel in nwaku and integrate
  • Use this channel in
    • func (w *Waku) checkForConnectionChanges()
    • func (w *Waku) handleNetworkChangeFromApp(state connection.State)
    • func (w *Waku) ConnectionChanged(state connection.State)
• DiscV5
  • In nwaku handle backoff with retry for when DNS Discovery fails to respond. (To obtain the bootnodes)
  • Make sure that when connection is lost, and regained after a while (30m or so), DiscV5 works
• Static nodes
  • In discoverAndConnectPeers directly connect to nodes from w.cfg.WakuNodes or attempt to use DNS Discovery if an enrtree is found
• Peer exchange
  • Use nwaku in runPeerExchangeLoop. Might not be necessary if nwaku already handles this?
• Relay
  • Subscribe/Unsubscribe from PubsubTopic
  • Receive messages
• Peers
  • Implement PeerCount (Currently in go-waku it returns the number of connected peers)
  • Implement func (w *Waku) DialPeer(address multiaddr.Multiaddr)
  • Implement func (w *Waku) DropPeer(peerID peer.ID) error
  • Implement func (w *Waku) PeerID() peer.ID

[gabrielmer]

Discv5 works after being disconnected for a long time - the bootstrap nodes are never removed from the routing tables. We can see the code here

However, after being online again, we don't attempt to connect to the nodes we already found because we have them in backoff period. When we are disconnected, our node thinks the other nodes are faulty because it can't connect to them, but in fact the faulty node is ours. When online again, because of this issue, our node doesn't attempt to connect to them.

We should create a mechanism to recognize when our node is offline and avoid attempting to connect to other nodes whenever that's the case, or at least avoid mischaracterizing well-behaved peers