fix(deserializer): try-catch, to prevent parsing non deserializable responses

[DopiGFX]

fix: add try-catch, to prevent parsing non deserializable responses

Problem

Requests answering empty Responses (like Pause Playback) are currently responding non-deserializable content.
This leads to a falsely thrown error.

Solution

I added a try-catch block to DefaultResponseDeserializer#deserialize to prevent the error.
I intentionally did not include logging in the catch-block because the error is falsely thrown.

Result

This only applies to Requests with empty Responses returning non-deserializable content.
It should not break any code

[DopiGFX]

This Pull Request should resolve the following Issues: #127 #119

[ellingtonjp]

Thanks for working on this! This fixes the specific issue in #127 and #119, but I think failing silently can mask future issues. For example, a future API bug could introduce malformed JSON in some other endpoint, and we'd have a harder time tracking it down since we wouldn't raise an error.

IMO this is really a problem in the API, and the API should be fixed. But in the meantime, perhaps we make it easier for clients to handle this (and future) bugs.

One option is to introduce a ResponseDeserializationError with a good error message to make it clear what's happening, and perhaps even including the response payload. This would give us the power to handle API bugs as necessary for our applications.

Thoughts?