[devworkspaces] maven-based tasks don't work in a container, created from universal developer image

[vitaliy-guliy]

Describe the bug

Maven don't work if it's a part of a task and is launched inside a container, created from universal-developer-image.

The problem faced when working on #20657

Che version

next (development version)

Steps to reproduce

1. Deploy Che on devworkpsaces
2. Create workspace using the devfile / repository https://github.com/vitaliy-guliy/java-guestbook/tree/run-maven-task
   ( should use quay.io/devfile/universal-developer-image:ubi8-112f94a )
3. Run maven-build-backend command fron My Workspace view
4. To play, run maven-test-backend command. It runs backend/test.sh script. It's possible to play with command and run them as a task.

Maven does not work for steps 3 ( screenshot 1 ) and 4.

5. Open a terminal in maven container, go to backend directory and run mvn install. Maven must be launched.

maven-test-backend prints a list of environment variables. Run export in maven container and compare both lists.

a) see the differences between PATH variables for both terminals (screenshot 2 and 3)
b) JAVA_HOME is missing for `maven-test-backend ( compare by hands when reproduce the bug )

---

Everything is working if maven container is created using quay.io/eclipse/che-java11-maven:next image.

Expected behavior

Working maven for quay.io/devfile/universal-developer-image:ubi8-112f94a.

Runtime

minikube

Screenshots

Screenshot 1. Launching of maven-build-backend command.

Screenshot 2. PATH variable for terminal with maven-test-backend command

Screenshot 3. PATH variable for maven terminal, that has been opened by hands.

Installation method

chectl/next

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response