JUnit 5: Impossible to override junit.platform.output.capture.stdout.* configurations

[RomanVlasenko]

Runner for JUnit 5 tests java/src/com/github/bazel_contrib/contrib_rules_jvm/junit5/ActualRunner.java (source) contains the following lines:

...
LauncherDiscoveryRequestBuilder request =
  LauncherDiscoveryRequestBuilder.request()
      .selectors(classSelectors)
      .configurationParameter(LauncherConstants.CAPTURE_STDERR_PROPERTY_NAME, "true")
      .configurationParameter(LauncherConstants.CAPTURE_STDOUT_PROPERTY_NAME, "true")
      .configurationParameter(
          Constants.EXTENSIONS_AUTODETECTION_ENABLED_PROPERTY_NAME, "true");
...

Unfortunately, it's impossible to override these settings, according to JUnit 5 documentation (source):

Configuration parameters are looked up in the exact order defined above. Consequently, configuration parameters supplied directly to the Launcher take precedence over those supplied via custom configuration files, system properties, and the default configuration file. Similarly, configuration parameters supplied via system properties take precedence over those supplied via the default configuration file.

Having these settings in place results in pollution of the test output, which can be quite annoying.

Would it be possible to remove hardcoded settings with LauncherConstants.CAPTURE_STDERR_PROPERTY_NAME and LauncherConstants.CAPTURE_STDOUT_PROPERTY_NAME or make them configurable via Bazel target attributes?