refactor(error): wrapped error responses print using debug formatting

[JosiahBull]

Reasoning

Debug formatting is preferred over Display as it will also print information about wrapped errors, including stack traces, which can make debugging much easier.

Note that this was already the case with UnexpectedResponse variant, this change standardises it across all error variants.

Alternatives

Debug formatting in a Display implementation is a bit of an anti-pattern. The Error type is using the same string formatting implementation for both it's Display and Debug traits. I can split up this functionality so that the Display information can be slightly less verbose if this is desired.