fix: improve the sanitization of credentials in local debug logs

[dotkas]

Pull Request Submission Checklist

• [x] Follows CONTRIBUTING guidelines
• [x] Commit messages are release-note ready, emphasizing what was changed, not how.
• [x] 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?

Removes some redundant logging we're already doing later in the flow.

Where should the reviewer start?

From the top.

How should this be manually tested?

N/A

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

N/A

[github-actions[bot]]

	Warnings
:warning:	Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones. A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax. Files found: ts-binary-wrapper/src/common.ts
:warning:	There are multiple commits on your branch, please squash them locally before merging!

Generated by :no_entry_sign: dangerJS against e88d202f839439ed3e73ddd8138744d33de98bb8

[snyk-io[bot]]

:warning: Snyk checks are incomplete. No issues have been found so far.

:warning: security/snyk check encountered an error. (View Details)

:warning: license/snyk check encountered an error. (View Details)

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