fix: improve peer exchange loop logic

[igor-sirotin]

Closes #6949
Closes #4628

Requires:

• fix: use simple protocol and pubsubTopic based selection for peerExchange waku-org/go-waku#1295

Description

Instead of running peer exchange each 5 seconds, run it on demand for specific shard

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	e6606b5	#1	2025-10-15 00:12:38	~3 min	macos/status-go	📦zip
✔️	e6606b5	#1	2025-10-15 00:13:11	~4 min	linux/status-go	📦zip
✔️	e6606b5	#1	2025-10-15 00:15:59	~6 min	windows/status-go	📦zip
✔️	e6606b5	#1	2025-10-15 00:19:53	~10 min	linux/nwaku	📦zip
✔️	e6606b5	#1	2025-10-15 00:22:16	~13 min	tests-rpc	📄log
✔️	e6606b5	#1	2025-10-15 00:36:30	~27 min	tests	📄log

[codecov]

Codecov Report

❌ Patch coverage is 62.96296% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.48%. Comparing base (c0f75d6) to head (e6606b5).

Files with missing lines	Patch %	Lines
messaging/waku/gowaku.go	62.96%	7 Missing and 3 partials ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #7005      +/-   ##
===========================================
+ Coverage    55.11%   59.48%   +4.37%     
===========================================
  Files          820      821       +1     
  Lines       116628   116647      +19     
===========================================
+ Hits         64275    69389    +5114     
+ Misses       45548    40169    -5379     
- Partials      6805     7089     +284     

Flag	Coverage Δ
functional	34.81% <62.96%> (?)
unit	55.14% <55.55%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
messaging/waku/gowaku.go	65.93% <62.96%> (+5.11%)	⬆️

... and 213 files with indirect coverage changes

[chaitanyaprem]

Iirc topic Health status for light/edge nodes where peer-Exchange is generally used is not implemented in go-waku. It is only implemented for relay mode.
Did you validate this in a setup and noticed that health is reported based on connections to Filter peers and available lightpush peers in peerStore?

that is how it is supposed to be derived as per #4628

- In lightMode: status-go shall derive it based on peer connections to Filter and lightpush(This shall be later migrated to SDK layer once https://github.com/status-im/status-go/pull/4665 is complete)

[igor-sirotin]

Hmm, weird. I did test it indeed and it looked like it's working 🤔

Let me double check carefully what's happening.

Thank you ❤️