Disallowing user to use incomplete fully qualified Check names in config file

[romani]

base on #4414 , #4387

code quality question was raised at #4430 (review) , see discussion from thsi comment and down for details.

What to do:

1. no changes to functionality is expected , except for disallowing to user use names like com.puppycrawl.tools.checkstyle.checks.naming.ConstantName, if user use fully qualified name, it should be absolutely correct ! Expected fully qualified Check name is com.puppycrawl.tools.checkstyle.checks.naming.ConstantNameCheck

2. Additionally there should refactoring to avoid logic that is based on catching reflection exceptions.
   We do have all information in collection like thirdPartyNameToFullModuleNames and NAME_TO_FULL_MODULE_NAME (at keys and values). So we could predict cases where will not have success to load class by reflection at createObject(code)

It is expected to have code like below(deliver to user all possible classpath issues):

    private Object createObject(String className) throws CheckstyleException {
        Object instance = null;
            try {
               Class<?> clazz = Class.forName(className, true, moduleClassLoader);

                final Constructor<?> declaredConstructor = clazz.getDeclaredConstructor();
                declaredConstructor.setAccessible(true);
                instance = declaredConstructor.newInstance();
            }
            catch (final ReflectiveOperationException  | NoClassDefFoundError  ex) {
                throw new CheckstyleException("Unable to instantiate " + className, ex);
            }
        return instance;
}

code:

        if (instance == null) {
            instance = createObject(name);
        }
        final String nameCheck = name + CHECK_SUFFIX;
        if (instance == null) {
            instance = createObject(nameCheck);
        }
        if (instance == null) {
 .....

should be extended to validate collection and call createObject only when we sure about success to load class.

[romani]

@djydewang , thanks a lot for elegant fix!