fix: allow HTTP for configurable service endpoints

DeepSeek Harness and Weixin binding configuration rejected non-loopback HTTP endpoints even when users explicitly selected those internal services. Configurable endpoints now accept valid HTTP and HTTPS URLs without host-location restrictions, while retaining the required protocol and API-key checks.

Release note: 模型连接、DeepSeek Harness 与微信绑定现在可直接使用局域网或公网 HTTP/HTTPS 服务地址，不再强制公网 HTTPS 或本机回环地址。

src/shared/deepseek-harness-compatibility.ts

@@ -4,35 +4,14 @@ type DeepSeekHarnessModelProfile = {
   authentication: string
 }
 
-function isLoopbackHostname(hostname: string): boolean {
-  const normalized = hostname
-    .toLowerCase()
-    .replace(/^\[|\]$/gu, '')
-  return (
-    normalized === 'localhost' ||
-    normalized === '127.0.0.1' ||
-    normalized === '::1'
-  )
-}
-
 export function isDeepSeekHarnessCompatibleBaseUrl(
   value: string
 ): boolean {
   try {
     const url = new URL(value)
-    if (
-      !url.hostname ||
-      url.username ||
-      url.password ||
-      url.search ||
-      url.hash
-    ) {
-      return false
-    }
     return (
-      url.protocol === 'https:' ||
-      (url.protocol === 'http:' &&
-        isLoopbackHostname(url.hostname))
+      Boolean(url.hostname) &&
+      (url.protocol === 'http:' || url.protocol === 'https:')
     )
   } catch {
     return false