Add e2e test case that checks publish-subscribe-query workflow across network nodes

[snormore]

Going to do another round or two on this before it's ready but putting it up for 👀 in the meantime

https://github.com/xmtp-labs/hq/issues/551

• The test case is pretty straightforward; grab the list of network nodes from nodes.xmtp.com, spin up a client node for each, subscribe to a topic on each, publish a message to each, expect that the messages are received via the subscription, expect that the messages are available via query, across all the nodes
• The test gets skipped in CI, and there's no automated running of it yet anywhere
• Needed to update go-libp2p to latest version for feat: allow dialing wss peers using DNS multiaddrs libp2p/go-libp2p#1592
• Moved some of the queryFrom and queryLoop logic into a store.Client because the Query interface on wakustore.Store was too restrictive with unexported fields on the args and results of it - it's also kind of weird that the logic that services requests was/is mixed together with the logic that makes requests / consumes the services of the protocol

I guess it's worth calling out that we can easily put a lot of messages into our dev/prod DBs with a continuous version of this, but I don't think we should optimize for avoiding intake of test data, and just make sure we have cleanup/maintenance code in place for invalid and known test topics in the DBs (https://github.com/xmtp-labs/hq/issues/609).

I'm not 100% sure how this kind of test works when clients need to authenticate, @jazzz maybe you can weigh in on that 🙏

[mkobetic]

Really nice. 👍