bug: respect set peers number

[weboko]

Problem

Due to this.connectedPeers being used directly -

Solution

Stop using it and cap amount of peers by passed config.

Notes

• Part of [Epic: js-waku] Reliability Protocol for Resource-Restricted Clients #2154

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku node	86.61 KB (+0.02% 🔺)	1.8 s (+0.02% 🔺)	8.1 s (-25.71% 🔽)	9.8 s
Waku Simple Light Node	154 KB (-0.07% 🔽)	3.1 s (-0.07% 🔽)	7.6 s (-51.49% 🔽)	10.7 s
ECIES encryption	22.83 KB (0%)	457 ms (0%)	3.2 s (-9.71% 🔽)	3.7 s
Symmetric encryption	22.33 KB (0%)	447 ms (0%)	1.7 s (-72.77% 🔽)	2.2 s
DNS discovery	72.26 KB (0%)	1.5 s (0%)	4.7 s (-22.04% 🔽)	6.2 s
Peer Exchange discovery	73.79 KB (0%)	1.5 s (0%)	12.1 s (-5% 🔽)	13.6 s
Local Peer Cache Discovery	67.57 KB (0%)	1.4 s (0%)	5.4 s (-39.75% 🔽)	6.8 s
Privacy preserving protocols	38.92 KB (0%)	779 ms (0%)	5.9 s (-3.39% 🔽)	6.7 s
Waku Filter	81.06 KB (+0.08% 🔺)	1.7 s (+0.08% 🔺)	9.3 s (+123.98% 🔺)	11 s
Waku LightPush	78.64 KB (+0.05% 🔺)	1.6 s (+0.05% 🔺)	6 s (-21.33% 🔽)	7.6 s
History retrieval protocols	79.08 KB (+0.06% 🔺)	1.6 s (+0.06% 🔺)	14.9 s (+78.89% 🔺)	16.5 s
Deterministic Message Hashing	7.31 KB (0%)	147 ms (0%)	987 ms (+18.19% 🔺)	1.2 s

[weboko]

Red herring. It is respected in the latest master but was not at https://lab.waku.org/dogfooding with @waku/[email protected]