Support volumes for components of type kubernetes/openshift

[metlos]

Subtask of #14970

Is your task related to a problem? Please describe.

To be able to share storage between different components of the devfile, it would be beneficial to be able to specify volumes on the kubernetes/openshift components the same way it is possible on the dockerimage components.

Describe alternatives you've considered

There are two possible solutions how to apply volumes:

1. Apply the volumes to all containers (matching the selector of the component). This might be dangerous because we might overwrite files that we don't want to in certain containers.
2. Use the same mechanism as for entrypoints of k8s/openshift components, e.g. have a parentSelector + containerName on the volume to limit where the volume should be applied on potentially per-container basis.

[mshaposhnik]

So there might be not very user-friendly message when volume defined in devfile matches any of the volumes defined in K8S/OS recipe (see below). So we cah either break workspace startup with more meaningful message, or just merge equal volumes to avoid messages at all. @metlos @l0rd WDYT?
Example:
Devfile:

...
components:
  - type: kubernetes
    reference: mongo-db.yaml
    volumes:
      - name: mongo-persistent-storage
        containerPath: /data/db

mongo-db.yaml:

spec:
        containers:
        - image: mongo
          name: mongo
          ports:
          - name: mongo
            containerPort: 27017
          volumeMounts:
              - name: mongo-persistent-storage
                mountPath: /data/db
        volumes:
          - name: mongo-persistent-storage
            persistentVolumeClaim:
              claimName: mongo-persistent-storage
-
  apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
    name: mongo-persistent-storage
  spec:
    accessModes:
     - ReadWriteOnce
    resources:
      requests:
        storage: 1Gi

Result:

[mshaposhnik]

So as for me, adding volume into devfile is an easy way to add volume into all containers without editing original recipe (when it's big or inaccessible for edit), so it looks logical just to add volume into all containers which did not containing it, and simply ignoring the ones which are already do contain.