KM225: Truncate client log

[yngvark]

Truncate client log to maximum 5000 bytes per log line.

Description

#436 truncated the server side log, this is client side.

This PR might crop useful info, but we'll try and see, and revert or adjust the "truncate max length" if that's the case.

Motivation and Context

Our logs are still full of noise, making it hard to read.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

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

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the release notes (for the next release).

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[codecov]

Codecov Report

Merging #444 (783f55f) into master (7f851e1) will increase coverage by 0.11%.
The diff coverage is 77.27%.

❗ Current head 783f55f differs from pull request most recent head 8594d03. Consider uploading reports for the commit 8594d03 to get more accurate results

@@            Coverage Diff             @@
##           master     #444      +/-   ##
==========================================
+ Coverage   25.87%   25.99%   +0.11%     
==========================================
  Files         206      207       +1     
  Lines        6264     6278      +14     
==========================================
+ Hits         1621     1632      +11     
- Misses       4643     4646       +3     

Impacted Files	Coverage Δ
pkg/client/core/api/rest/client.go	36.73% <0.00%> (-2.40%)	⬇️
pkg/middleware/logger/logger.go	90.90% <100.00%> (-1.69%)	⬇️
pkg/truncate/truncate.go	100.00% <100.00%> (ø)