Include the error code when reporting ClientConnectionExceptions

[dc-andy]

Feature description_

It would be useful for upstream systems to be able to automatically determine the type of error and react accordingly. e.g.

429 For Too Many Requests
Temporary error - Retry periodically

401 Unauthorized
Raise as a permanent error to be resolved by operator

This could be achieved by including the HTTP error code within ClientConnectionException.

I have raised a pull request to add and populate the code on ClientConnectionException here #2295

Currently the only way to determine the error type is to parse the message within the Exception - which may be subject to change in future.

[emillysilva65]

Including the HTTP error code directly in the ClientConnectionException is a solid approach to avoid reliance on parsing the exception message. Additionally, could you clarify which specific upstream systems you envision benefiting the most from this change?

[santiagorojas14]

ClientConnectionException needs the HTTP code as a direct property so callers can branch on 429 for retries versus 401 as fatal without scraping the message string that the issue says may change.