fix: do not use waku test fleet as default bootstrap (#2312)

The waku test fleet is unstable and should not be used as boostrap.

The issue is that DNS Discovery looks for "2" nodes and stop there. Meaning that if those "discovered" nodes are not reachable (ie, coming from test suite). js-waku does not connect.

Author: fryorcraken

packages/sdk/src/create/discovery.ts

@@ -10,7 +10,7 @@ import { type Libp2pComponents, PubsubTopic } from "@waku/interfaces";
 export function defaultPeerDiscoveries(
   pubsubTopics: PubsubTopic[]
 ): ((components: Libp2pComponents) => PeerDiscovery)[] {
-  const dnsEnrTrees = [enrTree["SANDBOX"], enrTree["TEST"]];
+  const dnsEnrTrees = [enrTree["SANDBOX"]];
 
   const discoveries = [
     wakuDnsDiscovery(dnsEnrTrees),

packages/tests/tests/waku.node.optional.spec.ts

@@ -18,10 +18,7 @@ describe("Use static and several ENR trees for bootstrap", function () {
     waku = await createLightNode({
       libp2p: {
         peerDiscovery: [
-          wakuDnsDiscovery(
-            [enrTree["SANDBOX"], enrTree["TEST"]],
-            NODE_REQUIREMENTS
-          )
+          wakuDnsDiscovery([enrTree["SANDBOX"]], NODE_REQUIREMENTS)
         ]
       }
     });