[Version] npm version detection should respect proxy settings

[TrueNine]

Bug Description

When users have a local proxy configured (e.g., via environment variables like HTTP_PROXY, HTTPS_PROXY, or npm config proxy), the npm version detection should respect these proxy settings. Currently, version detection may timeout without using the proxy, leading users to think there's a network issue when it's just proxy configuration.

Steps to Reproduce

1. Configure a local proxy (e.g., via npm config set proxy, environment variables, or system proxy)
2. Run CLI in an environment with restricted network but proxy available
3. Observe version detection timeout or failure

Expected Behavior

• npm version detection should use system proxy settings
• Timeouts should not occur when proxy is properly configured
• Clear error message if proxy is the issue vs actual network issue

Actual Behavior

• Version detection times out ignoring proxy settings
• Users may think there's a network issue when proxy just needs configuration

Additional Context

• Context: CLI (tnmsc)
• Related to version detection / network connectivity