Hard-coded -Xmx value in jvm.options prevents overriding Xms/Xmx externally

[Strzelba72]

In the file
sdk-gen/subprojects/java/flight-app/src/server/resources/wlp/usr/servers/defaultServer/jvm.options
the JVM heap-size flag is hard-coded (e.g. -Xmx1524m).
Because this file is processed after any environment variables or command-line
arguments, every attempt to override the heap size (via JAVA_TOOL_OPTIONS,
WLP_JVM_ARGS, Docker/Kubernetes run flags, etc.) is silently ignored.

Impact

• You cannot tune -Xms / -Xmx for different environments (dev / CI / prod).
• GC troubleshooting becomes harder because the heap size is fixed.
• OOM error when using large batches

Steps to reproduce

1. Build the application
2. Run app using -Xms more than 1536m