Feature: Configure Voyager as Circuit-Relay Node to connect browser nodes

[NiKrause]

I’ve been adding circuit-relay-server to the libp2p config:
https://github.com/orbitdb/voyager/blob/main/src/utils/libp2p-config.js

The goal was to enable browsers to connect to Voyager so they could discover each other and connect via WebRTC, using a direct connection upgrade with dcutr(). This might be very useful, when consumers running there own Voyager instance on their desktop or self hosted.

This normally simple config change, unfortunately, didn’t work in the end. No reservations could be made by the browsers — as if the circuit-relay was disabled. I initially suspected package incompatibilities, but I found that the exact same config and packages worked fine on a separate relay node.

This led me to suspect that the Voyager protocol might be interfering with the circuit-relay transport service. I started commenting out everything below line 70 in daemon.js:
https://github.com/orbitdb/voyager/blob/main/src/daemon.js#L70

Suddenly, the circuit-relay server started working as expected — it made reservations for two browsers, allowing them to discover and connect to each other. Unfortunately, even in this modified state, dcutr() still didn’t function properly. The two browser nodes disconnected after a 2-minute upgrade timeout.

For now, I’ll have to pause work on this, but I wanted to document it here.

[NiKrause]

upgrading
libp2p to 2.8.4

@libp2p/pubsub-peer-discovery to 11.0.1
@libp2p/circuit-relay-v2 to 3.2.10
@libp2p/dcutr 2.0.29
@libp2p/autonat 2.0.30
@libp2p/dcutr 2.0.29
@libp2p/circuit-relay-v2 3.2.10

Circuit-Relay is creating reservations just as usual and pubsub-peer-discovery is reporting new peers to the network.
Unfortunately dcutr doesn't seem to upgrade to circuit-relay connection to plain WebRTC between browsers as usual.
it reports:

InvalidMessageError: DCUtR connect message had no dialable multiaddrs

End the circuit connection still drops after the 2 minute timeout