Standardize the inconsistent logging, asserting, and println approach in JLM system tests

The reporting and error logging approach in JLM tests is inconsistent. Some of the tests generate "CSV" data files where some info is logged. The rest go into standard err and out. There are also some tests (e.g. VMLogger, where a log file is used to log detailed results of what the invoked Bean API's return. The output handling is not standardized in general.

This issue will track the work of standardizing the inconsistent logging, asserting, and println approach in JLM system tests

Start by reviewing the JLM system tests and the VMLogger example mentioned in the issue, then inventory where CSV files, standard output/error, assertions, println calls, and log files are used. Compare how each test reports results and identify the project guidance or test entry points that should define a consistent approach. Done means the affected tests follow an agreed reporting and assertion convention without losing detailed results.

Written by the indexing model from the issue text.