Voice calls fail when VPN routes are offered

### Steps to reproduce

1. Install element (can be from fdroid or app store)
2. Grant access to a wireguard VPN to element
3. Log into a matrix.org account
4. Make a voice call to another matrix.org user
5. Accept the call from the other matrix.org user
6. Wait

### Outcome

#### What did you expect?
The call should eventually connect.

#### What happened instead?
The call gets stuck at "connecting..."

### Comments on wireguard
This wireguard network provides no globally routable addresses, only providing `fd00::/8` RFC 4193 addresses. Termux, given access to this same VPN is able to ping both globally routable (e.g., google.com) and vpn addresses.

### Purpose
This may seem silly: just disconnect element from the VPN. However, I want to be able to access a homeserver that is only available on the VPN. Moreover, notice that I **am** able to access matrix.org, since I can indeed initiate outgoing calls (and send and receive text messages). I'm guessing the WebRTC code is insisting on using the VPN interface, and refusing to consider non-vpn interfaces.

### Your phone model

motox4

### Operating system version

Lineage (20-20240112-microG-payton)

### Application version and app store

1.6.10 (from fdroid)

### Homeserver

matrix.org

### Will you send logs?

Yes

### Are you willing to provide a PR?

Yes