tealdbg / algod interaction --- do not block, just log

Currently, when you use the WebDebuggerHook with tealdbg, then algod will block while the debugger process runs. This is certainly useful and powerful. But it is implausible to use when I am debugging the 8th transaction in a sequence of 20 transactions.

What I really want is just a way to collect the log of the transaction run annotated with the values at each step, like a dry-run does. (You could read this as a request to make it so there's an option to produce dry-run output on a live transaction)

But, I expect it would be relatively easy to have tealdbg retain all of the debugging steps internally, allow algod to progress, and then just use the web/cdt user interface to allow the user to browse what happened on the run (i.e. by single-stepping through it) but just turning off the ability to modify anything.