Improve FAQ in case of max peer reached on nim-waku

[D4nte]

Problem

The max limit of peers on nim-waku was set to 50. This has now been corrected to 150: https://github.com/status-im/nim-waku/issues/721.

Also, js-waku's default behaviour was to connect to all peers it found, it has been corrected to connect to 1 peer: https://github.com/status-im/nim-waku/issues/721.

As we only have 3 peers in the Status fleet (and no discovery mechanism yet in place), the fleet was rejecting connection after 50-150 users.

This is problematic because users and developers had to investigate a connect issue.

Solution

Better document the behaviour when a max connection limit is reached. Also review the default behaviour of js-libp2p: would it try to connect to a different peer instead?

https://github.com/status-im/js-waku/pull/294

Check if js-waku tries to open new connection when ping.

Also check what happens when we hit max peer and ask nim-libp2p. Also add to FAQ.

You can put a max peer setting and compile locally nim-waku to play with it.