Starting a new workspace with a clone of the specified branch doesn't work correctly if repo doesn't have devfile.yaml

[SkorikSergey]

Describe the bug

Starting a new workspace with a clone of the specified branch doesn't work correctly if repo doesn't have devfile.yaml.

Che version

7.87@latest

Steps to reproduce

1. Start a new workspace with a clone of the specified branch, for example from https://github.com/eclipse-che/che/tree/assets.

Expected behavior

Che repo on assets branch

Runtime

OpenShift

Screenshots

Installation method

chectl/latest

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

[olexii4]

@ibuziuk It is a regression after dropping the Devfile V1 support and removing the devfile-converter package eclipse-che/che-dashboard#1090.

It happens because che-server still returns Devfile V1 with the proper branch for a project:

But che-dashboard lost the ability to convert Devfile V1 into Devfile V2 without the devfile-converter package and using just a default Devfile.

I am sure that we should fix it on the che-server side. WDYT?