chore(logging): Unify debug log formats by using common logger for legacycli

[PeterSchafer]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

This PR re-uses the debug logger to log from the legacycli instead of logging itself to stderr. This way all logs go through our loggers and can be centrally configured.
The risk should be low.

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

[cursor]

Bug: Removed Sensitive Data Scrubbing from Stderr

The commit removes the logging.NewScrubbingIoWriter functionality, which previously scrubbed sensitive information from all stderr output. This introduces a security vulnerability where sensitive data (e.g., API tokens, credentials) can now be leaked in stderr. Specifically, when debug mode is disabled, stderr writes directly to os.Stderr without scrubbing, and when debug is enabled, it uses debugLogger which may lack equivalent scrubbing. Furthermore, in non-stdio cases, stdout remains buffered while stderr becomes unbuffered, potentially causing out-of-order output.

Locations (1)

• cliv2/pkg/basic_workflows/legacycli.go#L111-L124