Clean up / control behind a variable detailed routing algorithm output

[vaughnbetz]

These lines come out late in routing:
Router Stats: total_nets_routed: 15338 total_connections_routed: 83460 total_heap_pushes: 32806064 total_heap_pops: 15818505 total_internal_heap_pushes: 2761139 total_internal_heap_pops: 449373 total_external_heap_pushes: 30044925 total_external_heap_pops: 15369132 total_external_SOURCE_pushes: 0 total_external_SOURCE_pops: 0 total_internal_SOURCE_pushes: 60091 total_internal_SOURCE_pops: 40442 rt_node_SOURCE_pushes: 60091 rt_node_SOURCE_high_fanout_pushes: 2672 rt_node_SOURCE_entire_tree_pushes: 57419 total_external_SINK_pushes: 96678 total_external_SINK_pops: 96678 total_internal_SINK_pushes: 84140 total_internal_SINK_pops: 83460 rt_node_SINK_pushes: 0 rt_node_SINK_high_fanout_pushes: 0 rt_node_SINK_entire_tree_pushes: 0 total_external_IPIN_pushes: 457728 total_external_IPIN_pops: 234700 total_internal_IPIN_pushes: 2335801 total_internal_IPIN_pops: 222676 rt_node_IPIN_pushes: 206229 rt_node_IPIN_high_fanout_pushes: 124191 rt_node_IPIN_entire_tree_pushes: 82038 total_external_OPIN_pushes: 85443 total_external_OPIN_pops: 21303 total_internal_OPIN_pushes: 281107 total_internal_OPIN_pops: 102795 rt_node_OPIN_pushes: 139098 rt_node_OPIN_high_fanout_pushes: 11330 rt_node_OPIN_entire_tree_pushes: 127768 total_external_CHANX_pushes: 14442864 total_external_CHANX_pops: 7502984 total_internal_CHANX_pushes: 0 total_internal_CHANX_pops: 0 rt_node_CHANX_pushes: 296218 rt_node_CHANX_high_fanout_pushes: 101439 rt_node_CHANX_entire_tree_pushes: 194779 total_external_CHANY_pushes: 14962212 total_external_CHANY_pops: 7513467 total_internal_CHANY_pushes: 0 total_internal_CHANY_pops: 0 rt_node_CHANY_pushes: 307422 rt_node_CHANY_high_fanout_pushes: 97991 rt_node_CHANY_entire_tree_pushes: 209431 total_number_of_adding_all_rt: 701472 total_number_of_adding_high_fanout_rt: 26174 total_number_of_adding_all_rt_from_calling_high_fanout_rt: 3825

This should be leaned up or hidden behind some DEBUF flag.
If some is useful to typical users it could be put in a table instead.

Expected Behaviour

VPR's output should be comprehensible to the typical user and well formatted.

Current Behaviour

Router gives detailed info in what looks like a debug dump.

Possible Solution

1. Print only when requested by a debug variable or some such, or
2. Clean up the output into a nice table and make sure most users can comprehend it.

Steps to Reproduce

Run the router on a recent master branch (I used ~Nov. 15, 2023)

Context

Your Environment

• VTR revision used:
• Operating System and version:
• Compiler version: