[Feature request] Support full proxy URI parsing in TXT import (protocol://user:pass@ip:port)

[fuad00]

Problem

Currently, the TXT import dialog only parses proxies in IP:PORT format and requires the user to manually select a single protocol and optionally provide credentials — which are then applied uniformly to all imported proxies.

This is limiting when working with real-world proxy lists, where each line may have its own protocol and credentials. There is no way to import a mixed list without splitting it into separate files per protocol/auth combo and importing each one individually.

Expected behavior

The importer should be able to parse full proxy URIs in standard formats, for example:

socks5://user:password@192.168.1.1:1080
http://10.0.0.1:8080
socks5://another_user:another_pass@172.16.0.1:9050
http://user:pass@10.0.0.2:3128

When a line contains a full URI, the protocol and credentials should be extracted per-proxy rather than relying on the global fields.

Suggested formats to support

Format | Example -- | -- ip:port (current) | 192.168.1.1:1080 protocol://ip:port | socks5://192.168.1.1:1080 protocol://user:pass@ip:port | socks5://user:password@192.168.1.1:1080

The global Protocol / Username / Password fields could serve as a fallback for lines that only contain ip:port.

Use case

I personally maintain proxy lists in socks5://user:password@ip:port format and currently have to strip them down to ip:port before importing, losing per-proxy credentials in the process.