fix(android): clamp imported socksPort to valid range 1-65535

parseProfileFromJson read socks_port from imported JSON without any
bounds check, so a malformed or hostile profile could specify
socks_port: 99999 (or 0, or negative) and it would flow straight
into the exported config and the SOCKS5 client. Add coerceIn(1, 65535)
on the import path; default remains 1080 when the field is absent.

Found by ProfilesViewModelParseTest.clamps socksPort to 1_65535 range
during plan 001 baseline creation.

Author: Hidden-Node

android/app/src/main/java/com/gooserelay/gooserelayvpn/ui/profiles/ProfilesViewModel.kt

@@ -175,7 +175,7 @@ class ProfilesViewModel @Inject constructor(
             val name = root.get("name")?.asString ?: defaultName ?: "Imported"
             val debugTiming = root.get("debug_timing")?.asBoolean ?: false
             val socksHost = root.get("socks_host")?.asString ?: "127.0.0.1"
-            val socksPort = root.get("socks_port")?.asInt ?: 1080
+            val socksPort = root.get("socks_port")?.asInt?.coerceIn(1, 65535) ?: 1080
             val socksUser = root.get("socks_user")?.asString ?: ""
             val socksPass = root.get("socks_pass")?.asString ?: ""
             val googleHost = root.get("google_host")?.asString ?: "216.239.38.120"