lg-14790 handle network failures for socure

[AShukla-GSA]

🎫 Ticket

Link to the relevant ticket:
LG-14790

🛠 Summary of changes

Implemented handle_connection_error for socure requests

[theabrad]

LGTM

[amirbey]

1. can we add to DocAuth::Socure::Request

def handle_connection_error
  raise NotImplementedError
end

2. DocmentRequest.fetch is expecting a hash, so it seems like DocumentRequest#handle_connection_error should return a hash
3. similar to LN request, it looks like DocAuth::Socure::Request#handle_http_response should return handle_connection_error
4. can we add testing for the Socure standard and hybrid document capture controllers

[amirbey]

the caller of DocvResultRequest#fetch is currently receiving a hash, while it is expecting to receive a DocvResultResponse. it looks like we need to override Socure::Request#handle_invalid_response by creating DocvResultResponse#handle_invalid_response that returns a call to handle_connection_error(DocvResultResponse).

I noticed that the http response body (received from Socure) can be blank dependent upon the type of error (ie: invalid API key -- see screenshot). Otherwise, the API doc shows the body for other types of errors (400, 401) which can help us to determine how to process the http response when creating the DocvResultResponse.

[amirbey]

It'd be helpful to add some deeper testing (particularly in our controllers) to catch and protect against these types of scenarios 🤔

[amirbey]

LGTM ... thanks @AShukla-GSA 👍🏿