Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Installing the CLI always downloads from a hard-coded https://registry.npmjs.org/:

install: line 195, 199, 212
packages/gui-extensions/src/ssh/remote-cli.ts: line 79 (archiveUrl), 129 and 133 (latestBeta)

Behind a corporate firewall that only allows an internal mirror (Nexus, Artifactory, ...), Desktop can't install its CLI on SSH hosts: both the remote download and the upload fallback fail, so after every Desktop update the host shows as incompatible. The mirror serves the same tarball at the same path.

Proposal: use NPM_CONFIG_REGISTRY / npm_config_registry (trailing slash removed) as the base URL, falling back to https://registry.npmjs.org/:

• install: registry="${NPM_CONFIG_REGISTRY:-${npm_config_registry:-https://registry.npmjs.org}}"; registry="${registry%/}", then use $registry in place of the hard-coded URL.
• Desktop SSH bootstrap: build the download URL inside the remote script from the remote host's environment, the same way install does, since the remote host can reach a different registry than the Desktop machine. For the upload fallback and latestBeta, use the Desktop machine's registry via NpmConfig.registry(), which plugin installs already use.