Incorrect error message relating to default project

[sympatheticmoose]

/kind bug

Not severe. Just a bit of a gotcha which I keep hitting since I often run odo pointing at docker-desktop, but frequently kill docker when not in use. Partly relates to #4309

What versions of software are you using?

Operating System: macOS

Output of odo version: odo v2.0.3 (9ae7540)

How did you run odo exactly?

kube context set to docker-desktop, but not currently running docker
odo create [any]

Actual behavior

Error msg:
✗ You don't have permission to create or set project 'default' or the project doesn't exist. Please create or set a different project
odo project create|set <project_name>

Which is completely unrelated to the actual problem but seeing it as a fatal error reminds me to check docker is running, and sure enough that will fix it. Otherwise I'd guess a user would try that project create cmd, and then hit the connection refused error:
✗ Get "https://kubernetes.docker.internal:6443/apis/project.openshift.io/v1?timeout=32s": dial tcp 127.0.0.1:6443: connect: connection refused

Which is a bit clearer towards what the issue is, but still doesn't guide the user to resolve.

Expected behavior

Perhaps something similar to the check we had in Appsody which would give the following output on appsody init:
[Warning] Failed to check prerequisites: docker does not seem to be installed or running - failed to execute docker ps
...
[Error] Could not inspect the image: exit status 1: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Any logs, error output, etc?

[kadel]

The plan is to stop checking the cluster on odo create (#4096).
odo create should work even if the cluster is not running,There is no real reason why the cluster should be required for odo create.
The cluster connection should be required only once odo needs to perform or fetch information from cluster.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.