[bug] failed test when cargo test -- --test-threads=1 execute

[hitenkoku]

Describe the bug
failed test when cargo test -- --test-threads=1 execute

successed test when RUST_TEST_THREADS=1 cargo test exevute

[hitenkoku]

> cargo test -- -test-threads=1
...
failures:
    tests::test_exec_general_html_output
    tests::test_exec_none_storedstatic
    tests::test_overwrite_csv
    tests::test_overwrite_json
    tests::test_same_file_output_computer_metrics_csv
    tests::test_same_file_output_computer_metrics_exit
    tests::test_same_file_output_csv_exit
    tests::test_same_file_output_json_exit
    tests::test_same_file_output_logon_summary_csv
    tests::test_same_file_output_logon_summary_csv_exit
    tests::test_same_file_output_metric_csv
    tests::test_same_file_output_metric_csv_exit

---- tests::test_exec_general_html_output stdout ----
thread 'tests::test_exec_general_html_output' panicked at 'Command csv-timeline: Argument or group 'exclude-category' specified in 'conflicts_with*' for 'include_category' does not exist', 
...

[hitenkoku]

The error was due to the fact that the variable specified in conflict_with was not yet defined.

When the error was corrected, -test-threads was recognised as a hayabusa option when executed, resulting in an error.

I think that cargo test -- -test-threads=1 can also be supported if -test-threads is registered as a debugging option as a way

[YamatoSecurity]

I see, thanks for looking into this!