Issue Description :

To set a Workspace IDE, che-editor URL parameter option does not have a higher priority than .che/che-editor.yaml

Reproducer Steps :

I tried to reproduce this with below steps and found below observation :

Step 1] Set the defaultEditor to theia in checluster CR and was able to create a workspace with theia IDE by default :

defaultEditor: eclipse/che-theia/latest 

Step 2] Then created a repo with ".che/che-editor.yaml" and set :

id: che-incubator/che-code/insiders

Workspaces gets created with VScode IDE by default.

So found that option ".che/che-editor.yaml" has higher priority than setting "defaultEditor" parameter in checluster CR

Step 3] To check the priority of option "URL parameter for the workspace IDE" followed below steps :

• Set defaultEditor to theia in checluster CR
• Set ".che/che-editor.yaml" to eclipse/che-theia/latest
• Next tried to start workspace as per the below format :

https://devspaces-&lt;openshift_deployment_name&gt;.&lt;domain_name&gt;"#<git_repository_url>?che-editor=<editor_key>

Trying with URL paratmeter : che-editor=<editor_key>:

https://devspaces.apps.raunakbocp4.india.aws.cee.support#https://github.com/dipakkarde/che-demo?che-editor=che-incubator/che-code/insiders

But I found that workspace is getting created with "Theia" IDE only.

Further I also tried setting "defaultEditor" to VScode in checluster CR, But still workspace gets created with Theia IDE only.

So found ".che/che-editor.yaml" only having higher priority than other two options.

Additional Information :

Customers Use case :

customer is expecting that if we use the defaultEditor property in cheCluster, the IDE to be used (For exacmple : Theia) when spinning workspaces up is specified globally throughout the operator. However, If we choose to set a different IDE in .che/che-editor.yaml for a specific Git repo, workspaces spinning up will use this other IDE for this repo only. Then users can individually choose which IDE to spin a workspace up with using the che-editor URL parameter.