Include response in HTTPError for invalid refresh token

[NIR7cd]

Context:
The requests.exceptions.HTTPError exception has a response attribute which normally stores the response to which that error pertains. When manually creating an instance of requests.exceptions.HTTPError response is an optional argument that one can pass to the constructor in order to populate this attribute. This attribute can be useful to find out more about why the response is considered to be an error. For example, a user may want to do the following:

except HTTPError as e:
    log.error(f"Got error response with status code {e.response.status_code}")

Description of the Change:
This change modifies the error handling in Connection.update_refresh_token to make sure that the requests.exceptions.HTTPError that is raised when the refresh token is invalid has a valid response attribute.

Benefits:
Consumers can check for things like the status code and error message when they catch an HTTPError that XCC threw. This can be useful if consuming code wants to check specifically for an invalid refresh token and have different behavior based on that specific error. It also prevents code that checks for the response from getting an AttributeError when attempting to do so.

Possible Drawbacks:

Related GitHub Issues:

[Mandrenkov]

Thanks for catching this, @NIR7cd! The change and motivation are quite clear. 👍

I know this sounds pedantic, but do you mind modifying the following test to check that the response object is now included as part of the HTTPError?

TestConnection.test_update_access_token_failure_due_to_invalid_refresh_token()

[NIR7cd]

I have updated the TestConnection.test_update_access_token_failure_due_to_invalid_refresh_token() unit test to make sure that the HTTPError has the response attribute, and to make sure that the response attribute matches the expectation for what it should be in the case of invalid refresh token.

[Mandrenkov]

Thanks! Looks good to me. 🚢