chore: investigate interop test failures

[weboko]

Problem

Interop tests fail agains nwaku release candidate: wakuorg/nwaku:deploy-wakuv2-test

Main reason for that right now is - nwaku seems to be loosing connection to a peer for following tests:
Waku Filter V2 (Named sharding): Multiple PubsubTopics
Waku Store (named sharding), custom pubsub topic

For nwaku it seems to start failing from this waku-org/nwaku@897f487

Solution

Add missing parameters and throws to help catch similar issue in the future.

Upd

Looking into why go-waku still fails.

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku core	58.52 KB (0%)	1.2 s (0%)	349 ms (+67.21% 🔺)	1.6 s
Waku Simple Light Node	298.58 KB (+0.01% 🔺)	6 s (+0.01% 🔺)	610 ms (+28.29% 🔺)	6.6 s
ECIES encryption	31.97 KB (0%)	640 ms (0%)	176 ms (+17.2% 🔺)	815 ms
Symmetric encryption	31.96 KB (0%)	640 ms (0%)	79 ms (-46.18% 🔽)	719 ms
DNS discovery	106.77 KB (0%)	2.2 s (0%)	437 ms (+48.68% 🔺)	2.6 s
Privacy preserving protocols	145.17 KB (0%)	3 s (0%)	469 ms (+59.97% 🔺)	3.4 s
Light protocols	55.92 KB (+0.04% 🔺)	1.2 s (+0.04% 🔺)	195 ms (-24.25% 🔽)	1.4 s
History retrieval protocols	54.79 KB (0%)	1.1 s (0%)	238 ms (+37.36% 🔺)	1.4 s
Deterministic Message Hashing	5.92 KB (0%)	119 ms (0%)	76 ms (+44.13% 🔺)	194 ms

[fbarbu15]

LGTM