Created by: yzhoholiev
This PR resolves an issue with the ApiException error content described in #3473 (closed) .
The issue is linked to migration to the generic IRestResponse<T>. The deserialization happens before the exception is actually checked by ExceptionFactory.
Possible hotfix, for now, is to propagate both raw content from IRestResponse.Content as well as IRestResponse<T>.Data to the ApiResponse.
But I think it makes sense to roll back to the older implementation, where deserialization happed if an exception hadn't been constructed.