[Cloud Building] Sometimes dependency downloads fail when using other third-party npm registries.

### Build/Submit details page URL

_No response_

### Summary

Logs below are from cloud building.
```
npm error code ECONNRESET
npm error syscall read
npm error errno -104
npm error network read ECONNRESET
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly. See: 'npm help config'
npm error A complete log of this run can be found in: /home/expo/.npm/_logs/2025-09-09T05_16_50_317Z-debug-0.log
npm ci exited with non-zero code: 152
```

No doubt I'm using npm registry which hosted in China.
But I think you shouldn't upload package-lock.json for cloud building.
Maybe choosing a nearby registry is a better choice.
Or manually upload the entire project including node_modules.
**Some organizations may be using a private registry to host their own packages. And most of these registries are only accessible within their internal network.**

### Managed or bare?

No need for this field.

### Environment

expo-env-info 1.3.4 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 22.17.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.9.2 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-243.26053.27.2432.13536105
npmPackages:
expo: ~53.0.22 => 53.0.22
react: 19.0.0 => 19.0.0
react-dom: 19.0.0 => 19.0.0
react-native: 0.79.5 => 0.79.5
react-native-web: ^0.20.0 => 0.20.0
Expo Workflow: bare

### Error output

_No response_

### Reproducible demo or steps to reproduce from a blank project

The summary field covers everything about the issue.