Added tests at the end of build process, updated containers and command line program

[masesdevelopers]

Description

Added tests at the end of build process using an Apache Kafka server hosted in a service which uses the container based on KNet:

• the container was updated to host:
  • Server through environment variable KNET_RUNNING_MODE:
  • a standalone zookeeper/kafka server (KNET_RUNNING_MODE=standalone)
  • a zookeeper node (KNET_RUNNING_MODE=zookeeper)
  • a kafka node (KNET_RUNNING_MODE=broker)
  • CLI (KNET_RUNNING_MODE not set): the same container can start a CLI able to execute CLI commands or, with the right parameters, the Server side commands
• the container now uses a bash script as main entry point which manages the usage
• KNetCLI: removed the constraint on ClassToRun, if the switch is not available the first argument is used to decide which class invokes

Related Issue

closed #480

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [x] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[masesdevelopers]

The current test behavior fails in many execution and some one of them waits undefinitively for a subscription to become available