CannotResolveClassException should accept cause

For people writing custom converters/mappers they might encounter scenarios where class can't be resolved due to some other error. There is also a strong case for extending CannotResolveClassException instead of defining independent one (e.g. some mappers/converters/... may rely on catching CannotResolveClassException. Hence, it would be nice to have a constructor with cause.