Enabling the CircuitBreaker for remote HTTP cache

[AlexanderGolovlev]

This PR implements the feature to stop using the remote HTTP cache when it became unreachable.

The implementation is based on already existing CircuitBreaker logic. It includes the following changes:

• All non-retriable errors were counted as successful API calls. However, they include not only the cache miss errors (which should be considered as a successful call), but also the different connectivity errors (which should be considered as failures). To distinguish these errors, we have added the isSuccess predicate. HTTP_SUCCESS_CODES defines success codes for HTTP, and RemoteRetrier.GRPC_SUCCESS_CODES defines success codes for grpc.
• Current implementation of FailureCircuitBreaker defines the threshold required to calculate the failure rate: minCallCountToComputeFailureRate=100. In case of connection timeout errors this requires a very large time interval to reach the threshold, larger that the default experimental_remote_failure_window_interval=60s. To solve the problem, we have added one more threshold: DEFAULT_MIN_FAIL_COUNT_TO_COMPUTE_FAILURE_RATE=12. The value is chosen to be slightly more than number of failures within window interval with default experimental_remote_failure_rate_threshold=10.