Skip the loopback bind in t3 auth session issue

[jamesckim]

t3 auth session issue binds a loopback port even when it only talks to a server that is already running. A sandbox that denies listen on 127.0.0.1 then fails the command before any token is issued.

On current main:

• apps/server/src/cli/auth.ts runs every auth command through resolveCliAuthConfig.
• apps/server/src/cli/config.ts calls resolveServerConfig with mode and port unset. Unset mode becomes web. An unset port in web mode calls findAvailablePort.
• packages/shared/src/Net.ts implements that probe with server.listen on 127.0.0.1 (canListenOnHost, and reserveLoopbackPort when the preferred port is busy).

The desktop command does not start a listener. It issues, lists, or revokes a session for the existing app. The port probe is unnecessary there.

Observed on macOS with the Codex auto sandbox: the command dies with listen EPERM 127.0.0.1. The installed T3 Code (Beta) app is dated 2026-10-31 and still contains findAvailablePort. No token is issued.

Please skip that bind for t3 auth session issue, t3 auth session list, and t3 auth session revoke when they attach to an already running server. Use the running server's port, or skip port selection when the command does not start a listener.

This is not a request to allow the sandbox to bind. The command should not listen.