`odo deploy` doesn't immediately check for namespace existence

[dharmit]

/kind bug

What versions of software are you using?

Operating System: all

Output of odo version: main

How did you run odo exactly?

• Fresh minikube cluster
• The namespace myproject, which was mentioned in env.yaml, didn't exist on the cluster
• odo deploy for the devfile with outer loop components and devfile-nodejs-deploy example project

Actual behavior

odo deploy builds the image, but fails when creating Kubernetes components

Expected behavior

Should odo spend time building the image if the namespace doesn't exist?

Any logs, error output, etc?

$ odo deploy
  __
 /  \__     Deploying the application using devfile-nodejs-deploy Devfile
 \__/  \    Namespace: myproject
 /  \__/    odo version: v3.0.0-beta3
 \__/

↪ Building & Pushing Container: quay.io/tkral/devfile-nodejs-deploy:latest
 •  Building image locally  ...
build -t quay.io/tkral/devfile-nodejs-deploy:latest -f /home/dshah/src/devfile-nodejs-deploy/Dockerfile /home/dshah/src/devfile-nodejs-deploy
 ✓  Building image locally [2ms]
 •  Pushing image to container registry  ...
push quay.io/tkral/devfile-nodejs-deploy:latest
 ✓  Pushing image to container registry [1ms]

↪ Deploying Kubernetes Component: devfile-nodejs-deploy
 ✗  failed to create service(s) associated with the component: namespaces "myproject" not found

[dharmit]

@feloy do you think #6025 will/should handle this scenario as well?