HV-905 Providing a global config for auto unwrapping

An early attempt. Any thoughts on the direction?
> Why. I seem you get distracted by semantics here. I purely look at annotations and where they are placed.

LOL, "distracted by semantics", that's really a good one :) To me, all what counts is to create an API with clear and consistent semantics. Annotations and all the stuff are just means to create such an API.

> Because imo in one case it is implicit what you want to do, whereas in the other (IntergerProperty) it is not. 

Where in `@Min(3) IntegerProperty myInt` is it not implicitly clear what's meant here? There is no validator for (Min@IntegerProperty), there is an unwrapper for *Property, so the only way this makes sense is if the constraint is applied to the wrapped value.
If it helps to mitigate your concern, we may raise a definition error in case there is a validator for the wrapper type *and* unwrapper exists *and* unwrapping does not happen explicitly.

> Hmm. I find this consistent tbh. 

Ok, we seem to work with different definitions of "consistent" then :)

> Where is the problem with the implicit unwrapping?

There is no problem with it, and I didn't mean that `@UnwrapValidatedValue` should be required. On the contrary, I'd enable implicit unwrapping for both the cases once the global flag has been set, as an unwrapper exists in both cases.