HV-905 Providing a global config for auto unwrapping

An early attempt. Any thoughts on the direction?
> I just think one way or the other must be the default. 

That I am not sure about. I don't like to just apply the a default.

> Using the wrapper in this case seems reasonable to me. If you think it's of any help, we also can raise an exception in this case (validator for wrapped and wrapper is present) 

That is what I tried to suggest and you wanted me to describe more. All I am saying is that I want this ambiguous case to throw an exception. I think this is inline how BV generally handles multiple available constraint validators.  

> and add a boolean flag to @UnwrapValidatedValue which then can be used to resolve the case and say whether the wrapper (false) or the wrapped (true) is the target.

Interesting. That might work as well. I thought first of a new dedicated annotation, but a flag on `@UnwrapValidatedValue` would work as well.

> I'm fine with that 

Ok. Seems we might have found a consensus. 

> as long as we don't require @UnwrapValidatedValue to be given in all those cases where it safely can be assumed.

sure