Build Hamster should emit more detailed runtime JDK build information

[ChrisHegarty]

This change proposes to update the Build Hamster message so that it emits more detailed runtime JDK build information.

The additional build information about the runtime JDK is most useful when diagnosing test failures in jobs that execute JDK early access builds - trying to match the actual JDK in use when reading build scans. Currently we see 19-ea, which gives no indication of what actual 19-ea build is in use.

This change proposes to "stuff" the additional build information into the existing runtime JDK version message, but it could be easily put elsewhere or even into it's own Runtime JDK Build message if that would be more desirable.

Example:
BEFORE:

=======================================
Elasticsearch Build Hamster says Hello!
  Gradle Version        : 7.4.2
  OS Info               : Mac OS X 12.4 (aarch64)
  Runtime JDK Version   : 19-ea (Oracle)
  Runtime java.home     : /Users/chegar/binaries/jdk-19-ea.jdk/Contents/Home
  Gradle JDK Version    : 18.0.1.1 (Oracle)
  Gradle java.home      : /Users/chegar/binaries/jdk-18.0.1.1.jdk/Contents/Home
  Random Testing Seed   : 40C0F7FC177EC27A
  In FIPS 140 mode      : false
=======================================

AFTER:

=======================================
Elasticsearch Build Hamster says Hello!
  Gradle Version        : 7.4.2
  OS Info               : Mac OS X 12.4 (aarch64)
  Runtime JDK Version   : 19-ea (Oracle, 19-ea+26-2060)
  Runtime java.home     : /Users/chegar/binaries/jdk-19-ea.jdk/Contents/Home
  Gradle JDK Version    : 18.0.1.1 (Oracle)
  Gradle java.home      : /Users/chegar/binaries/jdk-18.0.1.1.jdk/Contents/Home
  Random Testing Seed   : 6A92036EEB4C7383
  In FIPS 140 mode      : false
=======================================

[elasticmachine]

Pinging @elastic/es-delivery (Team:Delivery)

[pugnascotia]

Change looks good IMO.

[ChrisHegarty]

@elasticmachine update branch

[breskeby]

lgtm

[ChrisHegarty]

@elasticmachine update branch