[Feature]: egress proxy for bot computers (browser + shell) #1481

Confirmation

• This is not a security vulnerability report

Description

Problem
Bot computers can't use a proxy, so on a self-hosted VPS they egress from a datacenter IP
and Cloudflare-protected sites block them.

Current state (verified on edge)

• supervisor-logic.ts -> computerCommandEnv() and computer-spec.ts ->
  containerCreateOptions() contain fixed env lists; nothing is forwarded.
• computer/rakazo-browser hardcodes Chromium's flags; no --proxy-server.
• HTTP_PROXY exists only for api/worker, not computers.

Proposed change

1. Proxy URL (http/https/socks5) in deployment settings, optionally per bot, stored with
   the existing encrypted secret store.
2. Add HTTP_PROXY / HTTPS_PROXY / ALL_PROXY / NO_PROXY to the computer's env so the shell,
   terminal, curl, pip, npm and git honour it.
3. Point Chromium at the proxy from rakazo-browser. Credentials can't go in
   --proxy-server, so either accept unauthenticated local endpoints only, or run a small
   per-computer relay that holds the credentials — which also enables per-bot exit IPs.

Notes

• Only native support can give individual bots different IPs; a host-level iptables
  redirect on a shared Team Computer gives one IP for all bots and only works for local
  Docker. (My workaround: gost + iptables REDIRECT on the rakazo-c* bridges.)
• No proxy configured should mean no behaviour change.

Steps to reproduce

.

Expected behavior

.

Actual behavior

.

Rakazo version or commit

latest

Operating system

Linux

SANDBOX_PROVIDER

No response

AGENT_RUNTIME

No response

Logs or screenshots