test: use cmd.exe for ProviderAuthScript on Windows

[bolinfest]

Why

The Windows ProviderAuthScript test helpers do not need PowerShell. Running them through cmd.exe is enough to emit the next fixture token and rotate tokens.txt, and it avoids a PowerShell-specific dependency in these tests.

What changed

• Replaced the Windows print-token.ps1 fixtures with print-token.cmd in codex-rs/core/src/models_manager/manager_tests.rs and codex-rs/login/src/auth/auth_tests.rs.
• Switched the failing external-auth helper in codex-rs/login/src/auth/auth_tests.rs from powershell.exe -Command 'exit 1' to cmd.exe /d /s /c 'exit /b 1'.
• Updated Windows timeout comments so they no longer call out PowerShell specifically.

Verification

• cargo test -p codex-login
• cargo test -p codex-core (fails in unrelated core/src/config/config_tests.rs assertions in this checkout)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: deba695a71

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Skip first token line when rotating Windows auth script

In ProviderAuthScript::new, more +1 tokens.txt > tokens.next does not remove the consumed token; per Windows more semantics, +<n> starts output at line n, so +1 starts at the first line. This leaves tokens.txt unchanged on each invocation, so Windows runs won’t ever surface the second token (e.g., refresh-path tests in auth_tests.rs/manager_tests.rs will keep reading the initial token and can fail or stop validating refresh behavior).

Useful? React with 👍 / 👎.

[bolinfest]

@codex review the latest version of this PR

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. You're on a roll.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".