[codex] Handle sync timeout in CLI

[chengzeyi]

What changed

• Detect sync-mode timeout errors from the SDK/API in wavespeed run --sync.
• Show a clear message that the task is still processing asynchronously.
• Include the prediction ID, result URL, and wavespeed show <id> query command in human output when available.
• Include sync_timeout, prediction_id, result_url, and query_command in --json error output.
• Update README command help and align the lockfile package version with package.json.

Why

The API no longer converts sync timeout into an async success response. A sync timeout means the task was submitted and is still queryable, so CLI users need an actionable error instead of a generic failure.

User impact

Successful run() output remains unchanged. On sync timeout, the command exits non-zero but gives users the prediction ID and query path.

Validation

• npm run lint
• npm run build
• npm run test:smoke
• git diff --check