Some early access Java version format doesn't support like "11.0.18-ea" in check-java.sh

Issue Summary

Some early access Java version format doesn't support like "11.0.18-ea" in check-java.sh .

This is reproducible on Data Center: yes

Steps to Reproduce

1. Step 1: Install early access Java version format like "11.0.18-ea". (not "11-ea", it is supported and working correctly)

   $ yum --showduplicates list java-11-openjdk
   
   $ yum install java-11-openjdk-11.0.18.0.9-0.3.ea.el8
   
   $ /usr/lib/jvm/jre-11-openjdk/bin/java --version
   openjdk 11.0.18-ea 2023-01-17 LTS
   OpenJDK Runtime Environment (Red_Hat-11.0.18.0.9-0.3.ea.el8) (build 11.0.18-ea+9-LTS)
   OpenJDK 64-Bit Server VM (Red_Hat-11.0.18.0.9-0.3.ea.el8) (build 11.0.18-ea+9-LTS, mixed mode, sharing)
   

2. Step 2: Change Java version which installed Step1. ref: How to change the Java version used by Jira "Linux/Unix"

   # DO NOT remove the following line
   #JAVA_HOME="/opt/atlassian/jira/jre/"; export JAVA_HOME
   JAVA_HOME="/usr/lib/jvm/jre-11-openjdk/"; export JAVA_HOME
   

3. Step 3: Start Jira via executing start-jira.sh

Expected Results

You can start Jira application via start-jira.sh.

Actual Results

You can't start Jira application via start-jira.sh without changes.

• Java version

  # /usr/lib/jvm/jre-11-openjdk/bin/java --version
  openjdk 11.0.18-ea 2023-01-17 LTS
  OpenJDK Runtime Environment (Red_Hat-11.0.18.0.9-0.3.ea.el8) (build 11.0.18-ea+9-LTS)
  OpenJDK 64-Bit Server VM (Red_Hat-11.0.18.0.9-0.3.ea.el8) (build 11.0.18-ea+9-LTS, mixed mode, sharing)
  

• execute start-jira.sh

  # ./start-jira.sh
  
  To run Jira in the foreground, start the server with start-jira.sh -fg
  executing using dedicated user: jira
  
                    `sMMMMMMMMMMMMMM+
                       MMMMMMMMMMMMMM
                       :sdMMMMMMMMMMM
                               MMMMMM
            `sMMMMMMMMMMMMMM+  MMMMMM
               MMMMMMMMMMMMMM  +MMMMM
                :sMMMMMMMMMMM   MMMMM
                       MMMMMM    `UOJ
     `sMMMMMMMMMMMMM+  MMMMMM
       MMMMMMMMMMMMMM  +MMMMM
        :sdMMMMMMMMMM   MMMMM
               MMMMMM    `UOJ
               MMMMMM
               +MMMMM
                MMMMM
                 `UOJ
  
        Atlassian Jira
        Version : 8.20.17
  
  
  If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-0820/Troubleshooting+installation
  
  
  Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
  Using CATALINA_BASE:   /opt/atlassian/jira
  Using CATALINA_HOME:   /opt/atlassian/jira
  Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
  Using JRE_HOME:        /usr/lib/jvm/jre-11-openjdk/
  Using CLASSPATH:       /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar
  Using CATALINA_OPTS:
  Using CATALINA_PID:    /opt/atlassian/jira/work/catalina.pid
  /opt/atlassian/jira/bin/check-java.sh: line 31: [: 11.0.18: integer expression expected
  /opt/atlassian/jira/bin/set-gc-params.sh: line 5: [: 11.0.18: integer expression expected
  Existing PID file found during start.
  Removing/clearing stale PID file.
  Tomcat started.
  

Workaround

• Use the bundled Java with Jira Installation
• Change the Java version

  # /opt/atlassian/jira/jre/bin/java  --version
  openjdk 11.0.13 2021-10-19
  OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
  OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode)
  

• (officially unsupported) Modify check-java.sh