Support devfile with more than one Kubernetes tool

Description

Devfile example:

specVersion: 0.0.1
name: fix-the-kube
projects:
  - name: nodejs-mongo-app
    source:
      type: git
      location: 'https://github.com/ijason/NodeJS-Sample-App.git'
tools:
  - name: theia-editor
    type: cheEditor
    id: org.eclipse.che.editor.theia:1.0.0
  - name: exec-plugin
    type: chePlugin
    id: che-machine-exec-plugin:0.0.1
  - name: mongodb
    type: kubernetes
    local: mongo-controller.yaml
  - name: nodejs
    type: kubernetes
    local: node-controller.yaml

Controllers yamls can be found at kubernetes example

[skabashnyuk]

@garagatyi @ibuziuk we are taking this issue to our sprint. @sleshchenko are going to work on it.

[garagatyi]

Since OSIO-Che and Che platform teams are not yet sure who will work on this issue we discussed technical details of the implementation with @sleshchenko We decided that scope of this task would be:

• devfile code should add tools content into recipe of type kubernetes list
• devfile code should convert dockerimage tool to k8s deployment or pod and also add it to the kubernetes list
• workspace start code should merge all the deployments/pods/os templates from this kubernetes list into a single deployment (since we don’t support multiple deployments yet)
• won’t implement export (was just confirmed by Mario)
• but add tool meta info into k8s objects to be able to implement export of them to devfile tools later (if needed)