Create specific KNetCore implementation for each application

[masesdevelopers]

    To fulfill the request we are changing the class chain:

• KNetCLI will have its own implementation of KNetCore<T>: the specific section of KNetCore<T> will be moved in the CLI implementation; this instance will not manage the Connect tools
• KNetPS will have its own implementation of KNetCore<T>: it will be a copy of the one in CLI
• KNetConnect will have its own implementation of KNetCore<T>managing only the Apache Kafka Connect with different command-line arguments:
  • instead to request ClassToRun with a value of ConnectDistributed or ConnectStandalone, the command-line interface will use d and s switches

Originally posted by @masesdevelopers in #135 (comment)