modularization of checks for non deploying container

@kpiwko @okiss would like to use these checks outside non deploying container but when he does not have ndc on class path he can not compile the code since check implements interface which is in ndc itself.

This leads to modularization of whole checks logic, currenty there are four artifacts:

1) ndc api which has interface one needs to implement
2) ndc imp which has api as dependency and there is implemented checks
3) ndc container which has ndc impl as dependency
4) ndc parent for all modules above

Now, one can have just api on class path and implement his own check without ndc.

@okiss does this sound ok for you?