test: Investigate inconsistent webRTC Interop Tests

[maschad]

          WebRTC tests seem flaky to me. I don't think this is a resource issue in CI. Running these tests locally (in compose and npm test) also sometimes fail for me.

Let's remove the webrtc tests for now, and add them back in when they're not flaky.

Originally posted by @MarcoPolo in #1809 (comment)

[danisharora099]

curious to know if there's an update on this or investigation around why these tests were flaky?
at @waku_org we have tests being flaky in a similar way where the peer:identify is not being triggered in the CI (mostly works locally, but also inconsistently doesn't trigger locally) and curious if these are related

@maschad

[maschad]

We should be able to re-enable these tests given the fixes merged in #2073

[achingbrain]

at @waku_org we have tests being flaky in a similar way where the peer:identify is not being triggered in the CI

This should be fixed by #2206 - specifically the stream that runs identify was sometimes being missed due to a race condition so the peer:identify event would fail to fire.

[maschad]

We can verify once libp2p/test-plans#310 is merged to confirm we have consistent webRTC interoperability

[maschad]

Closed by libp2p/test-plans#310