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?

With this change debug logs will redact Basic Authorization header if they would accour. While Basic Auth is not a common case in the CLI, there are edge cases where this could happen.

In addition, this PR updates the golang version from 1.23.8 to 1.23.10.

Where should the reviewer start?

snyk/go-application-framework#363

How should this be manually tested?

1. Stop docker daemon
2. snyk container test ubuntu:latest --username=us --password=pw -d
3. The debug logs must include Basic ***

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

N/A

Any background context you want to provide?

CLI-949