Update WakuClient peer Discovery

[jazzz]

The Current WakuClient uses static peer dialing to discover other nodes. This means that the other nodes must be known at startup which adds un-needed complexity.

To make it more usable, the following changes are needed

• WakuClient can send messages without knowing peerIds of all nodes
• WakuClient can discover new nodes after startup
• WakuClient should use existing waku discovery mechanisms

[jazzz]

Theres an open question of, what Waku network to use for messages. Given RLN ux is an open research topic, I'd suggest we avoid it. That means not using TWN.

The goal here is a developer preview of the API. Lets go with the solution gets two clients connected, requiring the least amount of engineering effort.