fix(v2ray): use dynamic port for SOCKS5 inbound instead of hardcoded 1080

[Sentinel-Bluebuilder]

Rebased onto current development (replaces #72, auto-closed after retarget from main→development due to base divergence). Single commit, same fix, cleanly rebased onto development HEAD 732bf85.

[Sentinel-Bluebuilder]

Revised per your feedback. The SOCKS port is now customizable instead of always auto-allocated:

• constructor(socksPort?: number) — pass an explicit port (e.g. 1080) to force a fixed, predictable SOCKS inbound; omit it (default 0) to keep the auto-allocate behavior.
• In parseConfig, findFreePorts(2) is now findFreePorts(needSocks ? 2 : 1) — when an explicit SOCKS port was requested we only allocate the apiPort.
• apiPort (internal stats inbound) stays auto-allocated either way.

One design note: I kept the requested port on the instance (this.socksPort) set in the constructor, and resolve the effective port in parseConfig. The alternative was a parseConfig(handshakeData, nodeAddrs, socksPort?) param. I went with the constructor because the SOCKS port is a property of how this client exposes its proxy, not of the per-handshake node data — it's known at construction time, whereas the WireGuard listenPort (in the sibling PR) only becomes relevant after the handshake. Happy to move it to the parseConfig signature if you'd prefer the two PRs to be symmetric.