Don't throw exception for missing EVCS validation

[t-ober]

Currently our ValidationUtils validation throws an Exception in case we pass a random entity or an evcs specifically for which we haven't implemented a validation method.

We should just log that we haven't implemented one yet and don't let the validation fail.

[sebastian-peter]

Hmm, I don't know if I agree here. If we don't throw there, one might just expect that some validation ran and succeeded, as it's easy to miss log statements.

Edit: Seeing that validation fails in total until this is fixed, I now get your point.

[staudtMarius]

@sebastian-peter Should we change throwing a NotImplementedException in generall? Because if we have other inputs, we might run into the same issue again.

[sebastian-peter]

@staudtMarius Yes, good idea. Contrary to what I said before here, I now don't consider a missing validation method a failure in the sense that corrupted input data leads to a failed validation.

So maybe buildNotImplementedException could be tranformed to a general notImplemented (or similar) method that just logs missing validation methods.