fix(hwlab): use domestic npm registry for node lanes (#825)

Co-authored-by: Codex <codex@noreply.local>

config/hwlab-node-lanes.yaml

@@ -442,8 +442,8 @@ networkProfiles:
         - 127.0.0.1
         - ::1
         - host.docker.internal
-        - registry.npmjs.org
-        - .registry.npmjs.org
+        - registry.npmmirror.com
+        - cdn.npmmirror.com
   node-local-vpn:
     proxy:
       http: http://127.0.0.1:10808
@@ -484,6 +484,8 @@ networkProfiles:
         - .debian.org
         - goproxy.cn
         - .goproxy.cn
+        - registry.npmmirror.com
+        - cdn.npmmirror.com
         - .svc
         - .svc.cluster.local
         - .cluster.local
@@ -511,6 +513,8 @@ networkProfiles:
         - .debian.org
         - goproxy.cn
         - .goproxy.cn
+        - registry.npmmirror.com
+        - cdn.npmmirror.com
         - .svc
         - .svc.cluster.local
         - .cluster.local
@@ -522,7 +526,7 @@ downloadProfiles:
       retries: 3
       timeoutSeconds: 240
     npm:
-      registry: https://registry.npmjs.org/
+      registry: https://registry.npmmirror.com/
       retries: 3
       fetchTimeoutSeconds: 120
     pip:
@@ -542,7 +546,7 @@ downloadProfiles:
       retries: 3
       timeoutSeconds: 60
     npm:
-      registry: https://registry.npmjs.org/
+      registry: https://registry.npmmirror.com/
       retries: 3
       fetchTimeoutSeconds: 120
     pip: