Rollback behavior for 4xx and 5xx status code.

[lucaslabari]

Goal

• In this PR we introduced some changes on the behavior when 4xx and 5xx status code is received.
• The change on that PR was not to retry when receiving those status codes because they are not expected to succeed on a retry.
• We are now rolling back that change because 2 functional tests failed and we plan to reintroduce these changes soon.

Testing

Covered by existing tests.

[codecov]

Codecov Report

Merging #82 (e596d22) into master (4c5ff31) will increase coverage by 0.07%.
The diff coverage is 33.33%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
+ Coverage   75.92%   75.99%   +0.07%     
==========================================
  Files         313      313              
  Lines       10114    10104      -10     
  Branches     1461     1455       -6     
==========================================
  Hits         7679     7679              
+ Misses       1843     1833      -10     
  Partials      592      592              

Files	Coverage Δ
.../android/embracesdk/comms/api/EmbraceApiService.kt	77.64% <33.33%> (+8.17%)	⬆️

[bidetofevil]

I'd consider just adding throws to the failure and payloadTooLarge blocks instead as the current behaviour doesn't throw if we get a 304 (even though the server doesn't return that right now I don't think for posts)