[Feature] Support IPv6 in Collaboration mode: desktop listener and mobile connection

[qwerrtyuiopasdf]

Is your feature request related to a problem? Please describe.

In Collaboration mode (Mirror), the desktop client currently cannot accept incoming connections from devices over IPv6, and the mobile app cannot connect to the desktop client via an IPv6 address. This causes significant inconvenience in modern network environments:

1. Desktop cannot listen on IPv6: When starting the proxy server in Collaboration mode, it appears to bind only to IPv4 addresses (e.g., 0.0.0.0). Devices that are assigned IPv6-only addresses or are on IPv6-preferred networks cannot reach the desktop client at all.
2. App cannot connect via IPv6: The mobile app only allows entering an IPv4 address (or hostname that resolves to A record) to connect to the desktop. If the desktop is on an IPv6-only LAN segment or the user wants to use a literal IPv6 address (e.g., [fe80::1]:9000), there is no input field or parsing support for it.
3. Workaround is painful: I have to manually disable IPv6 on the mobile device or rely on NAT64/IPv4 translation on the router, which is unstable and adds latency to packet capture.

Describe the solution you'd like

1. IPv6 listening support on Desktop
   Allow the proxy/collaboration server to bind to dual-stack or IPv6-only interfaces. Ideally:

   • Add an option in settings: "Listen on IPv6" or "Dual-stack (IPv4 + IPv6)".
   • When enabled, the server should bind to :: (IPv6 any-address) or specific IPv6 addresses, while still maintaining IPv4 compatibility (dual-stack).

2. IPv6 connection support on Mobile App
   Allow the mobile app to connect to the desktop using an IPv6 address or a hostname that resolves to AAAA records:

   • Support literal IPv6 address input in the collaboration connection dialog, e.g., [fe80::1]:9000.
   • Support hostname resolution that returns IPv6 addresses (currently seems to only resolve IPv4).

3. Display IPv6 address in Collaboration QR / connection info
   If the desktop has an IPv6 address, show it alongside the IPv4 address so mobile devices on IPv6 networks can scan/connect directly.

Describe alternatives you've considered

• Disable IPv6 on the mobile device: Forces the phone to use IPv4, but this breaks other IPv6-dependent apps and is not practical.
• Use an IPv4-only Wi-Fi network: Requires setting up a separate router or VLAN just for Reqable, which is overkill.
• Use a reverse proxy with IPv4-to-IPv6 translation: Adds an extra network hop and complicates SSL certificate handling for HTTPS traffic capture.

Additional context

• My desktop is on a corporate network that assigns both IPv4 and IPv6 addresses, but some mobile devices (test phones) are on an IPv6-only segment due to network policy.
• The current Reqable desktop version shows the IPv4 address in the collaboration panel, but netstat confirms it is not listening on IPv6 (:::port).
• Other proxy tools (e.g., mitmproxy, Charles) support dual-stack listening out of the box, so this seems to be a gap in Reqable's server socket initialization.