JAVA_OPTS is overriden during instrumentation

[esara]

Describe the bug
Somewhat similar to #1083 but for JAVA

To Reproduce
Steps to reproduce the behavior:

Prior to the instrumentation, we had in the entrypoint.sh

  JAVA_OPTS="$JAVA_OPTS
            --add-opens java.base/java.time=ALL-UNNAMED

which is needed for packages like java.time based on https://openjdk.org/jeps/396 with java17

but after the instrumentation

$ set|grep JAVA
JAVA_OPTS='-javaagent:/var/odigos/java/javaagent.jar -Dotel.traces.sampler=always_on -Dotel.logs.exporter=none -Dotel.exporter.otlp.protocol=grpc -Dotel.exporter.otlp.endpoint=http://192.168.1.112:4317/'
JAVA_TOOL_OPTIONS='-javaagent:/var/odigos/java/javaagent.jar -Dotel.traces.sampler=always_on -Dotel.logs.exporter=none -Dotel.exporter.otlp.protocol=grpc -Dotel.exporter.otlp.endpoint=http://192.168.1.112:4317/'

which results in

2024-04-18 13:33:58,966  WARN [qtp1662844977-6748] [DefaultHandlerExceptionResolver]   : Resolved [org.springframework.http.converter.HttpMessageNotWritableException: Could not write JSON: Unable to make field private final java.time.LocalDate java.time.LocalDateTime.date accessible: module java.base does not "opens java.time" to unnamed module @d453a986; nested exception is java.lang.reflect.InaccessibleObjectException: Unable to make field private final java.time.LocalDate java.time.LocalDateTime.date accessible: module java.base does not "opens java.time" to unnamed module @d453a986]

Expected behavior
It would be preferable to either append the JAVA_OPTS or have the options of not settings it

Additional context
JAVA_OPTS maybe set in the dockerfile again and not in the deployment/container env variables, unfortunate, but again, we may need to find a way to discover it from the process, similar to PYPATH