Provide a tool to inspect trace logs

Debugging correctness tests involves being able to understand what a system was doing from the emitted trace log file. There are a number of visualizations of information that can make this significantly faster and easier to do. Providing a common tool to do so would help other (potential) developers debug their failed tests.

The issue proposes a common tool for inspecting FoundationDB trace log files while debugging correctness tests. Start by reviewing the trace-log format and the information emitted during failed tests, then define which visualizations and workflows the tool should support. Done means developers can use the tool to understand system behavior from a trace log.

Written by the indexing model from the issue text.