.che/che-editor.yaml content is not taken into account when running a workspace

[azatsarynnyy]

Describe the bug

I noticed that the content of the .che/che-editor.yaml file is ignored when starting a new workspace.
The default editor is used. For our dogfooding instance, it's always che-code:insider.

Che version

next (development version)

Steps to reproduce

Spinup a new workpace from the following factory link:
https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#https://github.com/azatsarynnyy/java-spring-petclinic/tree/issue-demo?che-editor=eclipse/che-theia/next

Notice, that the che-code:insider editor is running.

Expected behavior

It should run either che-theia:next editor, as it's specified via the URL parameter (?che-editor=eclipse/che-theia/next),
or che-idea:next editor should be used, as it's specified in the .che/che-editor.yaml file.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

[azatsarynnyy]

Might be a related issue #21635

[vitaliy-guliy]

Might be a related issue #21635

Those issues have the same cause.
There is a pull request to fix the problem

[azatsarynnyy]

I've tested it and I'm not able to reproduce the bug anymore.
Thanks @vitaliy-guliy for fixing it.