RFR: 8349620: Add VMProps for static JDK [v3]

[Alan Bateman]

On Wed, 19 Feb 2025 21:05:47 GMT, Jiangli Zhou <jiangli at openjdk.org> wrote:

> * No `jlink` tool in `static-jdk` when running on static JDK. This is currently observable using the `static-jdk`.
> * No separate `lib/modules` file (and other JDK resource files) if we build a single hermetic Java image for the test. 

Once the efforts are further along then it will be necessary to ensure that tests that rely on bin/<tool> have the appropriate `@modules jdk.jartool` (or some other tool module) so that jtreg selects the appropriate set of tests to run. ToolProvider should work so tests that use this to run tools "in process" can execute. 

The jdk.static requires properties is slightly different, this is what will be used to select/not-select tests that can only run with a modular run-time image or static image. This includes tests that might rely on files in the JDK conf directory (user editable configuration files, not the same thing as JDK resource files as they will just work).

It's a bit premature to get into jlink here. A static image could include the jdk.jlink module but would only be useful when invoked with ToolProvider and with a module path that contains packaged modules that is can consume, and only if those packaged modules were created from the same src bits. There's a lot more to this for later phases of this effort.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/23528#issuecomment-2670648319