tools: option to run block generator test multiple times

[winder]

Summary

Optimizing for usage patterns. It is sometimes useful to run the same suite multiple times to account for transient DB behavior.

I'm using several scripts to run this tool. There may be other features from those scripts that should be migrated, but this seemed like a good start.

There are also some minor changes to logging to remove constant debug output and optimize for general usage.

Test Plan

1. Start a postgres container.
2. Run the command:

./block-generator runner \
    --conduit-binary /home/will/algorand/conduit/cmd/conduit/conduit \
    --report-directory reports \
    --test-duration 5s \
    --conduit-log-level trace \
    --postgres-connection-string "host=localhost user=algorand password=algorand dbname=generator_db port=15432 sslmode=disable" \
    --scenario generator/test_scenario.yml \
    --reset-db --times 5 --reset-report-dir

[codecov]

Codecov Report

Merging #5617 (f043a74) into master (d82691d) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5617      +/-   ##
==========================================
+ Coverage   54.95%   54.97%   +0.02%     
==========================================
  Files         460      460              
  Lines       64446    64446              
==========================================
+ Hits        35417    35432      +15     
+ Misses      26653    26644       -9     
+ Partials     2376     2370       -6     

see 13 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[tzaffi]

Nice change!

Now that the generator has a verbose flag, suggesting to use it for quieting some printouts, instead of commenting them out.