[Regression] Automatically restart from local devfile when devfile failed to be resolved at startup

[ibuziuk]

Describe the bug

This functionality is currently broken - #22491
There are situation where che-server is not able to resolve a devfile from a git repository using the git service API. A typical example is when it's not GitHub, GitLab, Bitbucket or Azure DevOps repository or when SSH URL is used.

Che version

7.95@latest

Steps to reproduce

Currently dashboard just proposes user to continue with the default devfile, which is not expected.

Expected behavior

• Dashboard adds attribute controller.devfile.io/bootstrap-devworkspace: true when Devfile resolution via API fails or is not supported by che-server - Add attribute controller.devfile.io/bootstrap-devworkspace: true when Devfile resolution via API fails or is not supported #22697
• Workspace startup continues using the default devfile
• The rest is done by DWO - Add ability for project clone to 'bootstrap' devworkspaces devfile/devworkspace-operator#1193 (project is cloned, devfile is found, and workspace is restarted automatically)

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

related DWO PR - devfile/devworkspace-operator#1193

[ibuziuk]

@dmytro-ndp we do need a test case for this scenario:

• SSH key is configured
• workspace started via private SSH URL
• workspace is started correctly based on the devfile from the private SSH repo.

N.B. no OAuth / PAT are configured

[dmytro-ndp]

@ibuziuk : could you please confirm, that there should be no any additional warnings during workspace startup via private SSH URL, such as the following, when SSH key is configured?: