feat: JVM release file parsing

[kateeselius]

Goal: Expand support for JVM vuln scanning by parsing the release file.

Jira Ticket:
Design Doc:

Discovered it is possible to parse the release file generated when Java is loaded in an image.

An example release file:

IMPLEMENTOR="Eclipse Adoptium"
IMPLEMENTOR_VERSION="Temurin-11.0.28+6"
JAVA_RUNTIME_VERSION="11.0.28+6"
JAVA_VERSION="11.0.28"
JAVA_VERSION_DATE="2025-07-15"
LIBC="gnu"
MODULES="java.base java.compiler java.datatransfer java.xml java.prefs ... etc"
..... other fields ...... 

This PR extracts the Java version from the release file and sends the version to registry to be scanned for vulns.

We have a separate scan result, keyBinariesHashes, that discovers java binaries within the image and will send a hash of the binary to registry. In registry, these hashes are attempted to be resolved to a package (named 'openjdk-jre') and version with a call to hash-lookup. A depGraph is generated from the matched java packages, with the package manager is "upstream". These naming conventions are set in order to match vulns with our db.

In registry, the extracted java version will be added to the keyBinariesHashes flow to be added to the depGraph and scanned for vulnerabilities. Since package names in the depGraph need to be unique, there can only be one 'openjdk-jre' package within the tree. This restraint means that we only add the java version parsed from the release file if there were no successfully matched hash-lookup binaries. In other words, this feature only supports one version of Java to be scanned.

Overview of Changes Within Snyk-docker-plugin:

1. Add JavaRuntimeMetadata Structure definitions.
2. Extraction Layer - create new extract action that is looking for the release file when scanning the image.
3. Analysis Layer - Parse the contents of the release file to extract the Java version.
4. Response Building - add the javaRuntimeMetadata fact to the first scanResult (handled not as a separate application scan, but part of the OS-level scan alongside keyBinariesHashes)

[bdemeo12]

Looks great !

One tiny general nit, there are a lot of comments in this PR. You could move the final design, and reasons as to why you chose to do xyz into a confluence doc, and clean up a lot of these comments!