Split the cms command from the 3scale-tools-cli

[hguerrero]

To evolve the CLI correctly, it would be good to move the CMS subcommands into another subcommand names cms. This way, we can start working on additional features, not only depending on the CMS API.

Today: 3scale-cms download
Proposed: 3scale[-tools|-ctl] cms download

[rmgrimm]

I like this idea... Thinking on it, however, it might be better to have a separate project that pulls in the 3scale-cms JAR as a dependency instead. That way this project/repository can remain focused on interactions with the CMS, with another project focused on providing the commandline interface to various 3scale features. Thoughts?

[hguerrero]

My experience with CLI development is limited, but having separate projects to import as modules makes sense. I'm curious if the sub-project needs to be able to execute on its own, meaning it has a TopCommand annotation or needs the import of the parent project.