feat(common): Client with conditional err handling

[Cobalt0s]

Current behaviour

When response status code is out of 2xx range we invoke ErrorHandler and operation returns golang error.

res.StatusCode < 200 || res.StatusCode > 299

Addition

The condition of what should be treated as "critical error" is for the connector implementation.
The change only enhances and fallbacks for current behaviour if no custom ShouldHandleError callback is provided.

For example:
Salesforce composite API may return 400 Bad Request with schema which we should parse in order to form BatchWriteResult. It is still a "happy path" from Ampersand point of view, because we populate data structure with errors, set status failure or partial failure, etc.

If provider treats it as "error" doesn't mean we do.

Note: there is ResponseHandler which alters http.Response but I prefer to keep it immutable, especially for the case I described.

[Cobalt0s]

• feat(codec): JSON Record decorator #2248 : 2 dependent PRs (#2233 , #2259 )
• feat(common): Client with conditional err handling #2247 👈 (View in Graphite)
• feat(common): BatchWrite helper methods #2246
• feat(datautils): Map deep copy + For Each #2245
• feat(common): Create BatchWriteResult #2244
• [ENG-2914] feat(salesforce): New Batch Adapter #2232
• [ENG-2914] feat(interface): BatchWriteConnector #2231
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.