Replace raw usage of fmt.Print with pcio.Print

[austin-denoble]

Problem

There's confirmation prompts where we're using fmt.Print directly rather than pcio.Print. We're going to be refactoring the pcio package more broadly, so for now just align the raw Print calls with the shim'd package.

Solution

Replace raw usage of fmt.Print with pcio.Print.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Infrastructure change (CI configs, etc)
• Non-code change (docs, etc)
• None of the above: (explain here)

Test Plan

There should be no user-visible change due to this code change.

---

Note

Low Risk
Low risk: small output-path changes for interactive prompts, with one error-message formatting tweak; no API or deletion logic changes.

Overview
Switches several destructive-action confirmation prompts (API key, project, organization, and local key prune) from fmt.Print to pcio.Print so prompt output respects the CLI’s pcio shim/quiet-mode behavior.

Also standardizes the input read error path in auth local-keys prune to use msg.FailMsg instead of printing directly to stdout.

^{Written by Cursor Bugbot for commit 4f97284. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}