Add a class parameter to DictionaryValuesResolver.

[ZhReimu]

Summary (Description of this PR)

Add a method com.power.doc.extension.dict.DictionaryValuesResolver#resolve(Class)
Use the javax.annotation.Nonnull annotation for several parameters and return values in DictionaryValuesResolver

Basic Example (PR Use Case)

public class BaseExceptionValuesResolver implements DictionaryValuesResolver {

    @NotNull
    @Override
    @SuppressWarnings("unchecked")
    public <T extends EnumDictionary> Collection<T> resolve(@NotNull Class<?> clazz) {
        return (Collection<T>) Arrays.stream(clazz.getDeclaredFields())
                .map(it -> fieldMapper(it, clazz))
                .filter(Objects::nonNull)
                .collect(Collectors.toList());
    }

    private EnumDictionary fieldMapper(Field field, Class<?> codeClass) {
        try {
            if (IAssert.class.isAssignableFrom(field.getType())) {
                IAssert anAssert = (IAssert) field.get(codeClass);
                return EnumDictionary.builder()
                        .setName(field.getName())
                        .setDesc(anAssert.getMsg())
                        .setValue(String.valueOf(anAssert.getCode()));
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
        return null;
    }

}

Motivation (Purpose of this PR)

Since we have already set valuesResolverClass, there is still a need to set enumClassName. Why not add the class obtained from enumClassName as a parameter in the DictionaryValuesResolver interface? Otherwise, being tied to a configuration feels uncomfortable.

Appendix: Not setting enumClassName will lead to NPE

java.lang.NullPointerException: Cannot invoke "java.lang.Class.isInterface()" because "enumClass" is null
    at com.power.doc.builder.ProjectDocConfigBuilder.getEnumImplementsByInterface (ProjectDocConfigBuilder.java:146)
    at com.power.doc.builder.ProjectDocConfigBuilder.initDict (ProjectDocConfigBuilder.java:141)
    at com.power.doc.builder.ProjectDocConfigBuilder.<init> (ProjectDocConfigBuilder.java:117)
    at com.power.doc.builder.ApiDocBuilder.buildApiDoc (ApiDocBuilder.java:72)
    at com.smartdoc.mojo.MarkDownMojo.executeMojo (MarkDownMojo.java:44)
    at com.smartdoc.mojo.BaseDocsGeneratorMojo.execute (BaseDocsGeneratorMojo.java:158)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:210)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:195)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:539)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1136)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:635)
    at java.lang.Thread.run (Thread.java:833)

[shalousun]

good