`oneOf` and `anyOf` errors where default values are present

Using `anyOf` or `oneOf` shouldn’t fill JSON object with defaults of non-matching subschemas.

Prior to this change, a JSON object validating against `anyOf` or `oneOf` would be mutated by each subschema with default values, even if that subschema then failed validation. These new properties would then be present in the JSON for validation against subsequent subschemas.

This pull request makes changes so that:

**On Success**
For `anyOf`, the defaults of the first matching subschema persist after returning from the call to `validate`.
For `oneOf`, the defaults of the only matching subschema persist after returning from the call to `validate`.

(It's not obvious what should happen for `allOf`. So we have not attempted to change behaviour here.)

**On Failure**
We set the JSON data back to the original data.


Ok, lets conclude that the tests are not complete with respect to how insert defaults should behave for ```anyOf```. The same possibly holds for ```allOf``` (what if more than one schema has a different default value for the same absent property).
Unfortunately the spec says nothing about defaults in ```allOf``` and ```anyOf``` (or I overlooked it). So we need to define the behaviour for ```json-schema ``` and therefore should make it explicit.