feat: sort peers for protocol by least active connections

[danisharora099]

Problem

Solution

Notes

• Depends on chore: use connected peers instead of discovered peers for protocols #1758
• Resolves
• Related to

Contribution checklist:

• covered by unit tests;
• covered by e2e test;
• add ! in title if breaks public API;

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku node	119.46 KB (+0.09% 🔺)	2.4 s (+0.09% 🔺)	675 ms (+30.07% 🔺)	3.1 s
Waku Simple Light Node	184.57 KB (+0.2% 🔺)	3.7 s (+0.2% 🔺)	662 ms (+23.53% 🔺)	4.4 s
ECIES encryption	23.16 KB (0%)	464 ms (0%)	132 ms (-59.94% 🔽)	595 ms
Symmetric encryption	22.61 KB (0%)	453 ms (0%)	130 ms (-13.12% 🔽)	583 ms
DNS discovery	72.6 KB (0%)	1.5 s (0%)	407 ms (+12.96% 🔺)	1.9 s
Peer Exchange discovery	74.68 KB (+0.27% 🔺)	1.5 s (+0.27% 🔺)	355 ms (-5.27% 🔽)	1.9 s
Local Peer Cache Discovery	67.8 KB (0%)	1.4 s (0%)	292 ms (+2.71% 🔺)	1.7 s
Privacy preserving protocols	38.91 KB (0%)	779 ms (0%)	226 ms (+50.97% 🔺)	1.1 s
Waku Filter	113.83 KB (+0.05% 🔺)	2.3 s (+0.05% 🔺)	477 ms (-5.89% 🔽)	2.8 s
Waku LightPush	111.81 KB (+0.13% 🔺)	2.3 s (+0.13% 🔺)	327 ms (-30.55% 🔽)	2.6 s
History retrieval protocols	112.27 KB (+0.17% 🔺)	2.3 s (+0.17% 🔺)	501 ms (+0.7% 🔺)	2.8 s
Deterministic Message Hashing	7.35 KB (0%)	147 ms (0%)	34 ms (+77.03% 🔺)	181 ms