When debug=true, show more details about refresh token failures
### Description

I'm currently debugging an issue where the same refreshToken is valid and works from my development environment (my house), but fails in production (hosted in fly.io). I have a feeling Ring started blocking fly.io servers in the last few days because otherwise there is no difference between these environments and this system has been working fine for over a year.

The only error I see in production is, even with debug=true:
`Error: Refresh token is not valid.  Unable to authenticate with Ring servers.  See https://github.com/dgreif/ring/wiki/Refresh-Tokens`.

I'd be great if I could see the raw error we are receiving from Ring when debug=true.

### Proposed solution

_No response_

### Alternatives

_No response_

### Device data

_No response_