test(hosted): match the allow-remote env var name case-insensitively

On Windows env var names are case-insensitive: run_isolated blanks
NPM_CONFIG_ALLOW_REMOTE before the test sets npm_config_allow_remote=none,
so the child sees a single variable under the first spelling and the
warning (which names the variable as the OS reports it) says
NPM_CONFIG_ALLOW_REMOTE=none. The product is right; the assertion was
POSIX-only. Fixes outer_npm_config_layers_are_respected on
test (windows-latest) after #251.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: mikolalysenko

crates/socket-patch-cli/tests/redirect_npm_allow_remote.rs

@@ -714,9 +714,15 @@ async fn outer_npm_config_layers_are_respected() {
         &[("npm_config_allow_remote", "none")],
     );
     assert_eq!(code, 0, "{stderr}");
+    // The warning names the variable as the OS reports it. Windows env names
+    // are case-insensitive, and `scan_hosted_env`'s blanking of
+    // `NPM_CONFIG_ALLOW_REMOTE` makes the child see that spelling there, so
+    // match the name case-insensitively.
     assert!(
         stderr.contains(&format!("Warning ({CODE}): "))
-            && stderr.contains("npm_config_allow_remote=none")
+            && stderr
+                .to_ascii_lowercase()
+                .contains("npm_config_allow_remote=none")
             && stderr.contains("would not take effect"),
         "{stderr}"
     );