Use DNS Discovery by default

[D4nte]

Problem

DNS Discovery is a more decentralized and flexible strategy than using the (hardcoded) predefineded Status nodes.
We expect node operators and platforms to use DNS Discovery (either Status' one or their own) until more dynamic discovery mechanisms are in place (such as peer exchange).

Definition of Done

• Confirm that nwaku native websocket support is now stable
  • Use the fleet test suite: Add test to confirm connection to test fleet #604
  • Try with web-chat, maintaining connection for 5min
  • Replace port in predefined node with the native one from nwaku instead of websockify and release.
• Include a live data (not enabled in CI) test that uses DNS peer discovery with createLightClient
• Use DNS Discovery in the web-chat example
• Set DNS Discovery as the default bootstrap method

[fryorcraken]

• peer exchange

[fryorcraken]

Use DNS Discovery in the web-chat example

Must be done first and some dogfooding needs to happen before we can consider dns discovery ready.

[danisharora099]

Use DNS Discovery in the web-chat example

Must be done first and some dogfooding needs to happen before we can consider dns discovery ready.

Wouldn't we need for the PR to be merged before we can test it in our example? How would we go about using an unmerged/unreleased version without building locally?
(#1114 (comment))

[weboko]

I think what @fryorcraken suggests is to hide if behind a feature flag so that consumers can pass an option and use experimental functionality intentionally without breaking old contract.

[danisharora099]

My bad.
The idea is to test DNS discovery before merging it as a default discovery mechanism. (#1114 (comment))

[danisharora099]

Update: DNS Discovery used in the web-chat example here waku-org/examples.waku.org#190

[danisharora099]

Merged!