Analyzing large files with the wt util isn't practical a lot of the time. wt dump and wt verify -d dump_pages both dump the full file and don't accept key range parameters to reduce the set of the file that is dumped.

This can result in a few issues:

• The dumped file doesn't fit on disk
• The dump takes a long time, and takes even longer to parse

We should support start_key and stop_key arguments for both of those utilities to resolve this issue in the future.

This should be implemented allowing each option to be provided without the other. I.e. if a start_key is specified but no stop_key is specified then the stop_key is assumed to be the end of the file and vice versa.