fix: NO_PROXY duplicated and inconsistent across configs

[dmzoneill]

NO_PROXY in compose has duplicate entries. Aliases NO_PROXY missing some hostnames present in compose. Deduplicate and align.

[github-actions]

Summary

I cannot locate any NO_PROXY configuration in the current repository. The repository at /home/runner/work/securetty/securetty only contains a single Python file (ai-responder.py) with no docker-compose files, shell scripts, or configuration files that would contain NO_PROXY settings.

The issue description mentions:

• compose (docker-compose files)
• Aliases (likely shell aliases or environment files)

Possible causes:

1. The issue may have been filed against the wrong repository
2. The configuration files haven't been pushed to the repository yet
3. The files might be in a different branch

To resolve this issue, please:

1. Verify this is the correct repository for the NO_PROXY configuration
2. Provide the file paths where NO_PROXY is defined (e.g., docker-compose.yml, .env, shell scripts)
3. Or push the missing configuration files to the repository

Once the files are available, I can help deduplicate and align the NO_PROXY entries across all configurations.