Fix incompatibility with rake 13.4+ verbose mode

[ogajduse]

Problem

Rake 13.4.0 introduced verbose console support by setting ENV["TESTOPTS"] = "-v" (ruby/rake#394). Rake 13.4.2 improved this to preserve existing TESTOPTS values and append -v only when not present (ruby/rake#723).

However, ci_reporter_test_unit was adding the test_unit_loader.rb file path to TESTOPTS, which caused conflicts:

Before rake 13.4.2:

• TESTOPTS was overwritten, breaking ci_reporter entirely

After rake 13.4.2:

• TESTOPTS preserved, but appending -v caused rake_test_loader to interpret the loader file as a test file
• Results in rake_test_loader: version unknown or <filename>: version unknown errors
• Affects projects using t.verbose = true in Rake::TestTask

Solution

Use RUBYOPT with Ruby's -r flag instead of TESTOPTS. This properly requires the loader before tests run, avoiding conflicts with rake's verbose handling.

Testing

Manually tested with:

• rake 13.4.2
• Rake::TestTask with t.verbose = true
• Verified XML reports are generated correctly
• Verified verbose output works when enabled

References

• Preserve ENV["TESTOPTS"] when verbose is enabled ruby/rake#723 - Fix that preserved TESTOPTS
• Verbose console ruby/rake#394 - Original verbose mode introduction
• Affects projects like theforeman/smart-proxy

Compatibility

This change is backwards compatible - RUBYOPT with -r works with all Ruby and rake versions.