WIP Revert "userland-proxy=false is not required anymore"

[sleshchenko]

What does this PR do?

This reverts commit b862e0e.

It follows the following email posted to che-dev https://www.eclipse.org/lists/che-dev/msg03375.html

Which minishift/minikube problems this PR fixes:

1. NodeJS + Mongo Devfile is working again. It can be fixed in an alternative way, and use localhost for application->DB communication.
2. If a user defines in their Devfile multiple Deployments and Service for setting up communication - it will work again. Like an example https://github.com/redhat-developer/devfile/blob/master/samples/web-nodejs-with-db-sample/devfile.yaml
3. Discoverable endpoints work again. User may declare them in dockerimage component. As an example, the NodeJS+Mongo Devfile referenced above.

⚠️ It's has WIP in the title because it was created to get feedback and concerns about requiring userland-proxy=false again

What issues does this PR fix or reference?

eclipse-che/che#14009

[benoitf]

I think you have valid arguments but other previous valid arguments were that restarting minishift or minikube with these settings need mostly to recreate the VMs and from UX it's not so nice to not be able to use the instance already there

[sleshchenko]

@benoitf

I think you have valid arguments but other previous valid arguments were that restarting minishift or minikube with these settings need mostly to recreate the VMs and from UX it's not so nice to not be able to use the instance already there

Should we print add like the following warning?

If you do specify `userland-proxy=false` then discoverable endpoints[see doc] in workspaces won't work. You can skip this checking by `--skip-userland-proxy-check`

Or maybe we even are able to do interactive option:

If you do specify `userland-proxy=false` then discoverable endpoints[see doc] in workspaces won't work.
Type `Y` if you are want to proceed without discoverable endpoints functionality:

Messages are just examples and definitely must be better.

[benoitf]

@sleshchenko is that che infra is able to check that a user is adding discoverable endpoints in its devfile, etc and then report that if userland-proxy=false it won't work as well ?

[sleshchenko]

@sleshchenko is that che infra is able to check that a user is adding discoverable endpoints in its devfile, etc and then report that if userland-proxy=false it won't work as well ?

Good idea, but I doubt that it can check it. chectl could provide this info for Che Server with env var.
BTW user then may face this issue with their own K8s components with multiple deployments and services