Fix tests using `OnStartupTriggeringPolicy`

The `OnStartupTriggeringPolicy` compares the creation time of the JVM with the creation time of the current log file.

However "creation time" is not well defined on UNIX systems and Java might output:

* `0L`,
* the time of last modification of the file,
* or the time the file was created, if the filesystem supports additional metadata (see for example [`statx`](https://man7.org/linux/man-pages/man2/statx.2.html) for Linux).

For the time being the tests have been disabled on some systems in 7b92b6f17965f96cbcd3caf404e9e553ded043ff and 53e3b85978fd0dc5bccee44adca7dc94b5c33679

Start with OnStartupTriggeringPolicy and the tests disabled by commits 7b92b6f17965f96cbcd3caf404e9e553ded043ff and 53e3b85978fd0dc5bccee44adca7dc94b5c33679. Compare how Java reports file creation time on UNIX systems and determine how the tests should behave across those environments. Done means the affected tests work reliably without assuming a single creation-time value.

Written by the indexing model from the issue text.