Consume new error/problem payload

[pturczyk]

This is the cli counterpart issue for pazuzu-io/pazuzu-registry#41.

A new error payload structure has been implemented in pazuzu-registry in accordance to application/problem+json which now needs to be properly consumed by the cli. Example payload:

{
   "type" : "http://pazuzu.io/error/fency_exception",
   "title" : "This is a fency exception", 
   "status" : 400,
   "detail": "Request was not fency enough to be fulfilled"
}

The mapping from the previous structure looks like following:

• "code" is now returned as part of the "type" URL
• "message" is now returned as "title"
• "detailed_message" is now returned as "detail"