CHE tomcat should not fail if KC is not accessible on starting

[riuvshin]

with changes introduced by this PR #8650
we have a regression that CHE server may completely fail during start-up if it will fail to connect to KC.
we added few workarounds which managed the right sequence of launching services but it will not cover a use case for instance with OSIO when we will need to restart CHE server and due to some reason it will not be able to connect to KC server on startup due to network issues or some other things.
I see two potential ways of solving that:

• refactor code and add an ability to retry to connect to the KC
• move everything that CHE is retrieving from KC to the configuration, and configure it before CHE start.

I prefer the first one because less to configure - easier to deploy / maintain

[skabashnyuk]

is this issue up to date?

[riuvshin]

yes, I think the problem is still there.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.