chore: publish CLI jar to central

[manikmagar]

This project uses groovy to for development. The default maven-javadoc-plugin does not generate javadocs for groovy classes. maven-javadoc-plugin generates jars for library and maven-plugin due to the generated sources by apollo graphql plugin and help mojo java files. But CLI module does not have any java files so javadocs doesn't generate there. This error caused maven central publishing to fail for CLI jar.

PR #54 skipped publishing CLI jar to Maven central for 1.2.0 version. For future releases, we may want to release CLI jar to central, in case any tooling needs to use the same class as CLI script to invoke the deployer. This provides the same validation to that integration as CLI script gets.

• [x] Fix java doc generation. (c0a2de176459bb15ea9fa2641759a24f35436d4d - Adding groovydoc-maven-plugin to generate javadocs from groovy as well as java.)
• [ ] Generate a shaded CLI jar?

[github-actions[bot]]

Unit Test Results

274 tests  ±0   274 :heavy_check_mark: ±0   1m 17s :stopwatch: +11s   31 suites ±0       0 :zzz: ±0    31 files   ±0       0 :x: ±0 

Results for commit c0a2de17. ± Comparison against base commit 0fab93a3.