MCP OAuth intermittently fails on Windows with socket error 10013

Describe the bug

OAuth authentication for a remote HTTP MCP server intermittently fails before the browser authorization flow opens.

OAuth authentication failed: MCPOAuthError: An attempt was made to 
access a socket in a way forbidden by its access permissions. (os error 10013)

Affected version

1.0.79

Steps to reproduce the behavior

1. Configure an OAuth-enabled remote HTTP MCP server without specifying auth.redirectPort.
2. Start a new Copilot CLI session.
3. Run /mcp auth <server-name>.
4. Authentication may fail while creating the local OAuth callback listener.

Expected behavior

Copilot CLI should select an available callback port. If binding fails, it should retry using another port and report the attempted port if all retries fail.

Additional context

Workaround

Pinning a known-available port and restarting Copilot CLI allowed authentication to complete:

"auth": {
  "redirectPort": 47000
}

The problem is intermittent. Authentication later worked without the override, possibly because credentials were cached or automatic port selection chose a usable port.

Environment

• Copilot CLI: 1.0.79
• Package: 1.0.79-9
• OS: Windows x64

从 /mcp auth 流程以及创建本地 OAuth 回调监听器的 auth.redirectPort 处理开始；在不覆盖端口的情况下，使用启用 OAuth 的远程 HTTP MCP 服务器在 Windows 上重现该失败。完成标准是：自动端口选择在 bind 失败后重试，并在所有重试都失败时报告尝试过的端口。