Standard Exception for Non-Deserializable

Currently the method `deserialize` does not define what shall happen in case a deserializer expects some particular JSON, but does actually find different JSON. This opens way for several outcomes:
* `return null`
* `return defaultObject`
* `throw RuntimeException`
* `throw `

In the current situation it is hard for application developers to use deserializers as he has to know what particular solution each particular deserializer chooses. So the outcome is not predictable nor similar.

From the view of an application developer it would be good if a general rule would be defined by JSON-B an application programmer can rely on, and a custom deserializer vendor can follow. My persion but unbias proposal would be to defined a standard exception for that case.

Start by reviewing the JSON-B deserialize contract and how custom deserializers currently handle JSON that does not match their expectations. Determine the standard exception behavior proposed in the issue and define what application developers and deserializer vendors should be able to rely on; done means the rule is agreed and specified consistently.

Written by the indexing model from the issue text.