Replace `@clusterRequired`

[datho7561]

It would be nice to fix the prompt to log in to a cluster when you perform an operation that requires a cluster but aren't logged into one. Currently, the prompt sometimes appears if you've never logged into a cluster on your computer (i.e. .kube/config is empty), but it doesn't count you as logged out if you've logged into a cluster and then logged out (i.e. you still have the cluster set as current-context).

We could use oc whoami to detect the current user and make sure it isn't system:anonymous (the username when not logged in). However, this will only work in OpenShift.

We could look into https://stackoverflow.com/questions/57004093/how-to-retrieve-current-user-granted-rbac-with-kubectl to see if that method is viable to detect if the user is logged on. eg. 'the user is considered logged on if they can create pods in the current namespace' or something similar.

[datho7561]

@JessicaJHee this might be an interesting medium-sized issue to look into if you need more to work on. The idea is that we have a decorator method called clusterRequired:

https://github.com/redhat-developer/vscode-openshift-tools/blob/main/src/openshift/openshiftItem.ts#L121

In this method, we parse the output of odo version to see if we are logged into a cluster. Specifically, we check to see that there is a line Server: followed by the API server's URL. This is flawed, since if you run odo logout, then you can still see the server listed in the output, but you cannot perform actions like odo dev.

Instead, we can use kubectl auth can-i create pod to check if we are logged in. This command checks if we can create pods in the current namespace (essentially, it checks if it's okay to run odo dev). You can also run oc auth can-i create pod, which does the same thing, but is easier to do since we bundle oc with the extension.

By decorating (adding @clusterRequired before) the methods where we declare commands, we can check if we are logged into a cluster before.

There are a few places where we have the decorator commented out, so as a part of this PR, it would be nice to uncomment the decorator.

[JessicaJHee]

@datho7561 Okay thank you for the guidance, I'm interested!