The goal of this issue is to make sure that all the devfile that are provided in the registry are tested and made compatible with devworkspace and in line with #679

Which area/kind this issue is related to?
/area registry
/area devworkspace

Stacks fixes:

• Use NON-terminating container components (PR)
• Replace ${PROJECTS_ROOT} with ${PROJECT_SOURCE} in commands workingDir
• Replace hardcoded /project(s) with ${PROJECT_SOURCE} in commands workingDir (PR)
• Add various mechanisms for preventing Eclipse Che breakages after updates in devfile GitHub org eclipse-che/che#21389

Samples fixes:

• Remove invalid buildguidance components
• Some container components use a non existing image (e.g. quay.io/eclipse/che-java11-maven:nightly).
• Use schemaVersion >= 2.1.0
• Remove projectStarter and project from the Devfiles in a git repository
• Sync devfile.yaml published at registry.devfile.io and the ones in the git repositories
• Sync latest stacks and samples devfiles