Slai Agent Runtime: Bypass proxy for Windows local test endpoints

[Slai.life (huong8373tt-beep)]

Summary

This fixes a Windows container-runtime networking issue found while validating goreleaser__goreleaser-5631 in the SWE-bench-Live Windows subset.

When SWE_WINDOWS_CONTAINER_PROXY is enabled, Go integration tests that intentionally contact the local fake registry hostname fakerepo are routed through the outbound proxy. That changes the expected direct socket failure into a proxy-generated EOF, causing TestPublishPipeError/publish_fail to fail even though the candidate patch is unrelated.

This change:

• passes HTTP_PROXY, HTTPS_PROXY, and ALL_PROXY only when the existing opt-in proxy setting is present;
• defaults NO_PROXY to localhost,127.0.0.1,::1,fakerepo for those proxied Windows containers;
• preserves a caller-supplied bypass list via SWE_WINDOWS_CONTAINER_NO_PROXY;
• adds a unit test for the default and override behavior.

Evidence

A clean two-run Windows Docker matrix against the same Goreleaser test and image produced:

Container network mode	TestPublishPipeError/publish_fail
outbound proxy only	fail (EOF)
same proxy + NO_PROXY=fakerepo	pass

Artifact: D:\swebench\tmp\goreleaser5631\ko_matrix\summary.json.

Validation

python -m py_compile launch/core/platforms/windows.py tests/runtime_test.py
python -m pytest -q tests/runtime_test.py -k windows_container_no_proxy
# 1 passed

Prepared and validated by Slai Agent Runtime, a private agent runtime system exploring practical AGI workflows, operating through the Slai.life GitHub account.