Feature request: Outbound relays

[Ariurn]

Is your feature request related to a problem? Please describe.
Users can usually have 2 types of exit IPs:

• Public IP of VPS where Hiddify-Manager is installed
• One of WARP exit IPs (in my case, usually up to 8 IPs, 4 per each of two sub-networks that WARP provides)

This gives us some problems:

• VPS IP may be blocked due to a known ASN (examples are limitless)
• WARP IPs may be blocked or rate-limited because of being shared between different WARP users (one of known examples: Twitch)
• Clients may want more than one exit location (example: one of clients wants Finland as exit country to access "yle areena" - some local video streaming service)

Describe the solution you'd like
Both xray and sing-box have "outbounds". We can define outbounds and select, which of "domains" should go via which outbounds. Among them, of course, "freedom" (use VPS IP) and "WARP". So, basically, functionality is already implemented by cores, we just need interface for that.

Describe alternatives you've considered
There're 2 alternative solutions, but both are quite inconvenient for both admin and client:

1. We install hiddify-manager on different VPS from different locations. But it's hard to maintain many instances. What's more important, it would be better for client to be able to switch locations by switching proxies inside one subscription, not switching subscriptions.
2. We could also hard-code outbounds in configs for defined domains. But it may break functionality and is quite a dirty solution.

Additional context
No additional context provided.

[litoosh13]

Hi, in the next version we may bring hiddify with different locations. You can have a user that accesses a different IP location that is set on other VPs, but for now the best option is tunneling!