In WT-6302, we moved the format test program's operations tracing into a WiredTiger log so operations tracing could scale to longer runs. While a separate database is used by default for operation tracing, the primary WiredTiger database can optionally be used instead.

It would be useful to add a configuration where WiredTiger verbose messages could be redirected to the WiredTiger log in the same way. This would (1) give us a single trace stream with individual thread IDs and timestamps, allowing us to trace format operations both inside and outside of WiredTiger, and (2) allow verbose messages to scale with longer runs, that is, log archival would allow us to retain just the most recent set of verbose messages, so it would be possible to turn on verbose messages on long WiredTiger runs.