Improve team management actions and document curl dependency

[hansaes]

Summary

• fix team invite / revoke / remove flows and make Teams page updates optimistic so actions no longer stay stuck in loading
• add Windows CREATE_NO_WINDOW handling so team management no longer flashes a curl.exe console window
• add docs/zh-CN/report/团队管理依赖系统-curl-说明.md to explain that team management currently depends on system curl, why that dependency exists, and how to use / proxy it

Why team management still depends on curl

• the team endpoints are under https://chatgpt.com/backend-api and behave more like browser traffic than ordinary API requests
• current implementation sends browser-like headers and maps CODEXMANAGER_UPSTREAM_PROXY_URL directly to curl --proxy
• in challenged / Cloudflare-sensitive environments, this path is currently more reliable than a plain internal HTTP client

How to use

1. Ensure curl / curl.exe is available in PATH
2. Open the Teams page and use sync / invite / revoke / remove actions normally
3. If upstream is sensitive, set CODEXMANAGER_UPSTREAM_PROXY_URL=<proxy> or pair it with the repo's curl_cffi / WARP helper scripts
4. If curl is missing, team-management RPC calls will fail early with failed to execute curl...

Test Plan

• node --test tests/teams-page-filters.test.mjs tests/transport-web-commands.test.mjs
• pnpm run build:desktop
• cargo check -p codexmanager-service --tests
• cargo test -p codexmanager-service background_process_creation_flags_hide_windows_console --lib
• cargo build --bin codexmanager-service