bug: pubSubTopic not respected on createLightNode

[mfw78]

This is a bug report

Problem

When trying to initialise a node object in Javascript, the pubSubTopic parameter isn't being used to configure the pubSubTopic. This appears to be a regression with the most recent release.

Code example:

	const waku = await createLightNode({
		defaultBootstrap: false,
		libp2p: {
			peerDiscovery: [bootstrap({ list: BOOTSTRAP_LIST })],
		},
		pubSubTopic: "/waku/2/dev-waku/proto",
	});

Then, when conducting a simple ping-pong test, the nwaku node that was in BOOTSTRAP_LIST indicates:

INF 2023-07-29 07:20:03.757+00:00 received filter subscribe request          topics="waku filter" tid=1 file=protocol.nim:110 peerId=12D*tk5oPx request="(requestId: \"fca4ad27-1ce0-4bfb-81a9-62797f4f5368\", filterSubscribeType: SUBSCRIBE, pubsubTopic: some(\"/waku/2/default-waku/proto\"), contentTopics: @[\"/swarm-waku/1/pong/proto\"])"

The actual behaviour that I expect is that the pubsubTopic should be set to /waku/2/dev-waku/proto.

Proposed Solutions

pubsubTopic is respected.

Notes

• js-waku: "@waku/sdk": "^0.0.16", "@waku/interfaces": "^0.0.15"
• Environment: browser (firefox)
• Nodes connected to: local nwaku v0.0.18

[fryorcraken]

Cc @danisharora099 who is looking at static sharding

[danisharora099]

@mfw78 can you please share reproducible code? #1586 should address this bug