Validate inverse remove strategy SET_NULL against column nullability

[beikov]

When having an updatable inverse collection, it might happen that the SET_NULL inverse remove strategy is used which won't work if the mapped by columns are non-nullable. This is especially problematic because SET_NULL is the default strategy. The current error a user sees is that a non-null constraint is violated which isn't very useful. This should be checked during metamodel building.