expose debugging flag to CLI

[CodyCBakerPhD]

relevant but does not close #4

@oruebel Per your question on debugging #5 in the run command, this adds a CLI flag --debug that show display tracebacks

NOTE 1: that relies on the tracebacks actually triggering due to an error in the test case itself - I don't think it capture errors in the setup

NOTE 2: for the internet dependent tests, and this is especially prevalent for fsspec on my device, the tests can show up as 'failed' without any traceback if they hit the maximum timeout value. This can be configured per test I believe, as an attribute on the class similar to the repeat value (which if the test is expected to take a long time, you might want to limit anyway)

[CodyCBakerPhD]

I also exposed the --bench flag so you can run your new subtests without running the rest of the suite

[oruebel]

Thanks @CodyCBakerPhD