The downstream issue is https://issues.redhat.com/browse/CRW-2640

Synced from Eclipse Che issue

https://github.com/eclipse/che/issues/20857

When devWorksapce is enabled, the k8s configuration file should be injected into each container - https://github.com/eclipse/che/issues/20782.

So, in devWorkspace we don't need openshift-authentication-plugin to login into the cluster.

When devWorkspace engine is enabled, we have to provide another che plugin vscode-openshift-connector without che-openshift-authentication-plugin: https://github.com/eclipse-che/che-plugin-registry/blob/main/che-theia-plugins.yaml#L361-L379

Releases Notes Text

Users OpenShift connection token gets automatically injected in the workspace pods as startup and the OpenShift Connector VS Code extension leverages that now. This was already working with the Che server and we have aligned the DevWorkspace based workspaces too.