Support openshift Devfile components (the same way as kubernetes components)

[rm3l]

/kind feature

Stumbled upon this while working on #5451

Which functionality do you think we should add?

openshift components should have been deprecated and removed from the Devfile specification, but this is currently not the case. So odo should support them.

Why is this needed?

At this time, running odo deploy with an openshift component does not output any error/warning messages, and does not deploy the component either, which seems quite confusing.
For example, running odo deploy with the following devfile.yaml succeeds with the following message: Your Devfile has been successfully deployed, but nothing was actually deployed.

After a discussion with @kadel:

So there is a history behind openshfit component in devfile. It was there in devfile v1, and it got carried over to devfile v2, but the decision was made that it doesn't make much sense to have both openshift and kubernetes components when they are doing the same thing and that having just kubernetes component is ok.
But it looks like it was never deprecated from the spec.
That is why it was never implemented.
But because it looks like it was never deprecated, and removing it would mean breaking change in spec, we will have to support it now.

[rm3l]

Grooming (2023-01-19)

• Idea to make odo convert OpenShift components into K8s components right after parsing the Devfile. Beware of side effects
• Implement as simple case .. which should behave the same way as K8s components.

[rm3l]

After starting pair programming on this issue today, we noticed that running "odo dev" with a Devfile containing an OpenShift component would create this resource on the cluster, but immediately delete it afterward. This seems due to #6189, because only Kubernetes components are being loaded from the Devfile.
So we need to fix this behavior.

After digging further, we'll also need to check all places where Devfile K8s components are being loaded and handle OpenShift components accordingly. So this might affect the following commands as well:

• describe component: we need also to show OpenShift components in the human-readable output
• delete component: resources created for OpenShift components are currently not detected as candidates for deletion
• dev: K8s components not referenced by any apply command are automatically created by odo dev. This should also be the case for OpenShift components.