[DSET-4072] Include (truncated) response body in the error message in case we fail to parse the response body

[tomaz-s1]

This pull request updates apiCall() function to also log partial raw response body in case we fail to parse response body as JSON.

This will help troubleshooting various edge cases when the API doesn't return valid JSON.

[codecov-commenter]

Codecov Report

Merging #29 (064dbca) into main (8d16acf) will increase coverage by 0.31%.
The diff coverage is 92.11%.

@@            Coverage Diff             @@
##             main      #29      +/-   ##
==========================================
+ Coverage   73.42%   73.72%   +0.31%     
==========================================
  Files          10       10              
  Lines        1358     1370      +12     
==========================================
+ Hits          997     1010      +13     
+ Misses        302      299       -3     
- Partials       59       61       +2     

Impacted Files	Coverage Δ
pkg/client/add_events.go	84.14% <57.14%> (+0.28%)	⬆️
pkg/client/client.go	85.48% <100.00%> (+0.49%)	⬆️

[tomaz-s1]

I noticed build failed the first time during CI/CD run so I assume there is still some kind of race condition going on during the tests.

[tomaz-s1]

I pushed another change so we also log addEvents URL which is used in the errors to make troubleshooting easier.

In ideal world, we would refactor this code some more and have base struct / class for API errors which would carry all the context (response status code, body, endpoint url, request method, etc.) and utilize this everywhere for consistent and useful log and error messages.

[martin-majlis-s1]

But otherwise looks good. :)

[tomaz-s1]

I added two more test cases - one to assert actual error logged / returned by the client (c04072b) and one to cover API endpoint URL handling (761f154), so this should now be ready for a final review.