fix(logging): prevent crashes when using debug and trace level logging

[CatalinSnyk]

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 handles type conversions and errors when formatting logging timestamps, returning an empty string is definitely better than crashing the CLI run.

This also lands a change from code-client-go that removes some redundant trace logs for request bodies; and also a GAF change for limiting the size of request bodies that are logged. All of those should fix some crashes when using the CLI with debug logs and trace level enabled.

Where should the reviewer start?

Main changes here are early returning in case of type conversion error when casting the interface to a string; and I also added an early return in case the time string formatting fails, just for good measure.

How should this be manually tested?

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

This should fix some crashes when the CLI was used with debug and trace logging level enabled.

[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)