+++ This bug was initially created as a clone of Bug #2025592 +++

Created attachment 1843026 [details]
devconsole samples with invalid devfiles

## Description of problem:

The devfiles that are included in 4 ODC samples are invalid. 

The component image build guidance has an invalid container image:

```
  - name: buildguidance
    attributes:
      tool: console-import
    container:
      image: buildguidanceimage-placeholder
      memoryLimit: 1024Mi
      endpoints:
        - name: http-3001
          targetPort: 3001
```

The problem is that Eclipse Che (or any tool that supports devfile v2) will try to pull the image and fail when trying to start a workspace based on those samples.

We have opened an issue on the [devfile registry side](https://github.com/devfile/api/issues/666) but if the fix happens on the devfile registry repo only, OSD will get broken. A fix should be provided OSD-side as well. 

## Prerequisites (if any, like setup, operators/versions):

OCP 4.9 (and previous releases of ODC that support devfiles)

## Steps to Reproduce

Deploy Eclipse Che on an OCP cluster
Create an application from one of the samples with at devfile
Click on the Eclipse Che link on the topology view

### Actual results: Che workspace startup fails.
### Expected results: Che workspace should start successfully.

## Reproducibility (Always/Intermittent/Only Once):

Always

## Additional info:

Eclipse Che versions prior to 7.39 and CodeReady Workspaces before 2.13 didn't support devfile v2. But that got fixed.
https://issues.redhat.com/browse/CRW-2411