Allow passing envs in POST /sandboxes/{id}/connect

[terzioglub]

⏺ Is your feature request related to a problem? Please describe.
Cannot pass new env variables when resuming a sandbox.

Sandboxes are often reused across long-lived sessions. Secrets injected at creation time (e.g. OAuth tokens, GitHub App installation
tokens, short-lived cloud credentials) expire well within the sandbox's lifetime — GitHub installation tokens, for example, expire
after 1 hour. Once expired, any process inside the sandbox that relies on $GITHUB_TOKEN (git pull/push, API calls, etc.) fails with
401.

Today the only workaround is to pass the refreshed secret as a command argument on every exec, which leaks it into process lists,
shell history, and logs. There's no way to update the sandbox's env after creation.

Describe the solution you'd like
Extend POST /sandboxes/{sandboxID}/connect to accept an envs field in the request body. Values would be merged into the sandbox's
env and applied to processes started after the resume.

curl --request POST
--url https://api.e2b.app/sandboxes/{sandboxID}/connect
--header 'Content-Type: application/json'
--header 'X-API-Key: '
--data '{
"timeout": 1,
"envs": {
"GITHUB_TOKEN": "ghs_..."
}
}'

This mirrors the envs field already supported on sandbox creation, and would let callers rotate short-lived secrets without leaking
them through command arguments.

[linear]

ENG-3833

[penggegegege]

⏺ Is your feature request related to a problem? Please describe.

---

🚀 解决方案

这个问题通常可以通过以下步骤解决：

1. 检查环境配置 - 确认所有依赖已正确安装
2. 查看官方文档 - 访问 Allow passing envs in POST /sandboxes/{id}/connect #1279 了解详情
3. 社区搜索 - 类似的 issue 可能已有解决方案

📖 完整文章：https://openclaw-d4gvfpwo18fe40c09-1254186748.tcloudbaseapp.com/e2b-dev-E2B-1279.html

💡 提示：如果问题仍未解决，请在 issue 中提供完整的错误日志，我会继续跟进。