fix(connector): inherit shared proxy and bound startup

[enderzcx]

Summary

• normalize conventional proxy environment variables (including lowercase and ALL_PROXY) and resolve the host system proxy through Electron on every desktop platform
• add one shared HTTP(S) proxy transport for Node HTTP(S), WebSocket SDKs, Undici, Telegram, and Discord
• bind Connector health immediately while adapters start, cap each adapter bootstrap at 30 seconds, and preserve concrete startup failures as degraded health
• make bundled grammY/node-fetch cancellation compatible and keep runtime retries finite

Root cause

The Connector child already inherited proxy environment variables, but grammY/node-fetch and Discord's REST stack supplied their own transports and bypassed Node's environment/global proxy behavior. Telegram could then wait on grammY's long API timeout and retries before the service ever bound its health port.

Verification

• npx tsc --noEmit
• pnpm test — 469 files passed, 1 skipped; 3892 tests passed, 9 skipped
• pnpm build
• Connector service typecheck and targeted suite — 9 files / 27 tests
• pnpm test:connector-replay
• pnpm test:connector-service
• Settings → Connectors browser walk in demo mode; no console errors and no secret values read
• unsigned pnpm electron:smoke:workspace; all packaged Workspace receipt checks passed and the temporary app was cleaned
• bundled Connector smoke with an existing sealed Telegram configuration reached awaiting_link after identity validation and command publication; no test notification was sent
• Discord public gateway REST probe through the shared dispatcher returned HTTP 200

Scope and safety

• supports HTTP and HTTPS proxy endpoints; SOCKS-only rules remain unsupported
• no broker/trading path changed
• no outbound notification test, credential change, or real-account mutation was performed

[vercel]

@enderzcx is attempting to deploy a commit to the luokerenx4's Team Team on Vercel.

A member of the Team first needs to authorize it.