chore: investigate peer:identify timeouts

[weboko]

This is a bug report

Problem

After migration to libp2p #1400 it appeared that waiting for peer:identify is decreasing the reliability of peer exchange tests significantly. Locally it is passing but in the pipelines it times out.

Proposed Solutions

Investigate why it started happening more often (it was happening before) and what can be done to bring this testing back since some consumers of js-waku might rely on the event and the presence of the protocol.

Notes

Commit with the test - 32f6650

[danisharora099]

@danisharora099 observed that the tests failed occasionally before the upgrade as well; perhaps the libp2p upgrade made it more unreliable.
the general idea maybe can to investigate WHY this is even happening, while other tests work.

for eg:
dns compliance tests have not shown any unreliability in terms of success.

[danisharora099]

@weboko while I agree that I have witnessed Peer Exchange compliance tests failing in the CI occasionally (and works on reruns randomly); testing with the commit/test you attached above, I am unable to repro this: #1467

I'm continuing to investigate particularly from compliance test point of view.

Update: #1468 should help!

[danisharora099]

closed with #1468