When a devfile references a parent we should not add the default component

[l0rd]

Is your enhancement related to a problem? Please describe

When a devfile has parent (full sample):

schemaVersion: 2.2.0
metadata:
  name: inventory-quarkus
parent:
  id: java-maven
  registryUrl: https://registry.devfile.io/
  version: 1.2.0

the resulting Pod has 3 containers (the gateway, the one defined in the parent and the default one):

$ kubectl get pods <pod-name> -o json | jq -r '.spec.containers[].image'
registry.access.redhat.com/ubi8/openjdk-11:latest
quay.io/devfile/universal-developer-image:ubi8-38da5c2
quay.io/eclipse/che--traefik:v2.9.6-bb7be8d50edf73d8d3a812ac8873ef354a0fe9b40d7f3880747b43a3525855d2

Describe the solution you'd like

The default component (the universal-developer-image in the case above) should not be added if there is a parent.

[ibuziuk]

would be nice to backport it to Dev Spaces 3.5

[l0rd]

Now I cannot even start a workspace

[ibuziuk]

Reopening, reproduced the same issue with https://github.com/che-incubator/quarkus-api-example/tree/parent that references https://registry.stage.devfile.io/viewer/devfiles/community/udi

[ibuziuk]

We investigated the issue with @olexii4 and it looks like the problem is on the devworkspace generator end cc: @svor

Basically, when devfile contains the parent reference we should not fail with the error.
N.B It is important to backport the fix to 7.64.x for Dev Spaces 3.6 cc: @nickboldt

[ibuziuk]

@l0rd should be fixed and also backported to 7.64.x for 3.6
verifed on dogfooding against che-incubator/quarkus-api-example#40