Application Helm Chart

[johnholiver]

This PR initializes a helm chart with multiple subcharts to map the given application.
Considering the restriction that the "Play with Docker" solution should continue to work, I've made tried to match the base images that make the project docker images to images that are used by the most prominent Helm charts used as dependencies. This match passed the acceptance tests (which are executed in docker).

The application doesn't properly execute on k8s yet, altho all deployments are considered healthy and the web interface is accessible. One of the main difficulties in following up with the project is missing a good grasp of each service state. It would be positive if the main server and the consumers could:

• be queried for its health
• be guaranteed to fail for all necessary but missing EnvVars (with logs)
• log immediately after they reach a state in which they are ready to enact their functions (e.g. consumer gets connection with all dependencies, inform that connection has been established for each, and send one more message when last resource is acquired, and enter an idle/ready state).
  Moreover, the approval of the images/dependencies updates would produce more security to continue the work here. Being something that can even be split in a separate PR if needed.

Extra changes:

• moving away from user guest for rabbitmq (facilitates bitnami/rabbitmq usage)
• moving the grafana dashboards storage location within the target docker image (in k8s, /var/lib/grafana path is quite reconstructed based on chart configuration)
• written a guide on how to setup a k3s cluster and what is necessary to do after to deploy the chart