[Pulsar SQL] Add workaround for Presto 332 java.version parsing issue

[lhotari]

Fixes #14951

Motivation

• See Pulsar SQL won't start with Java 11.0.14.1 #14951

• Presto 332 cannot parse a version string with more than 2 dots, such as 11.0.14.1

Modifications

• Add a workaround in bin/pulsar startup script that overrides the java.version system property with a version with 2 dots in it. This is applied to "sql-worker" and "sql" commands.

[nicoloboschi]

LGTM
verified the script locally with zulu distro of 1.8,11,17

nicolo.boschi % ({ java -version 2>&1| head -1 | awk -F" '{ print $2 }' | awk -F. '{ print $1 "." $2 "." $3 }' | grep -v -F ..; } 2>/dev/null)
11.0.13

nicolo.boschi % sdk use java 8.0.322-zulu
nicolo.boschi % ({ java -version 2>&1| head -1 | awk -F" '{ print $2 }' | awk -F. '{ print $1 "." $2 "." $3 }' | grep -v -F ..; } 2>/dev/null)
1.8.0_322

nicolo.boschi % sdk use java 17.0.1-zulu
nicolo.boschi % ({ java -version 2>&1| head -1 | awk -F" '{ print $2 }' | awk -F. '{ print $1 "." $2 "." $3 }' | grep -v -F ..; } 2>/dev/null)
17.0.1

[eolivelli]

Lgtm.
This is a great hack

I hope that it will work for future java versions

[lhotari]

The solution doesnt work yet, I'll debug it later

[lhotari]

This solution won't work. It would require a Java agent to override the "java.version" System property. I think it's better to upgrade Presto and just support Java 11, PR is #14953 .