Websocket relay does not relay pubsub messages (except pub-sub peer-discovery)

[silkroadnomad]

e.g. in hotel wifi's where Webrtc is restricted through some firewall, (connection is established via Websocket), relay establishes the WebSocket connection to browser peers

The peers create a Webrtc swarm successfully

• not confirmed anymore 15.03.2024 - location Komune
• confiremd 25.05.2024 - location ekb coworking

Unfortunately, if any peer publishes a pub-sub message no other peer can listen and react to it. (except probably the relay, which doesn't relay it via WebSocket).

Mobile networks:
In mobile networks on the other hand this works perfectly (via webrtc then)

Test:

• in an environment where peer-to-peer connections are blocked (peer-to-peer pub-sub doesn't work) which if that counts for both a WebRTC only connected peers and also for a Websocket only connected peers.

• 25.05.2024 (location ekb coworking) - successfully webrtc only connected swarm (via Rust WebRTC relay) but NO pubsub on deContact topic but OrbitDB replicates successfully (via pubsub)

• 25.05.2024 (location ekb coworking) - successfully websocket only connected swarm (via Websocket relay) but NO pubsub on deContact but OrbitDB replicates successfully (via pubsub)

• check if websocket relay can subscribe to a peers topic manually.

• make sure / clarify a websocket relay is able to relay pubsub messages via websocket if peers are not already connected via webrtc

[silkroadnomad]

using circuit-relay transport fixed the issue (latest commit)