Show executing SQL statement in long-running query log message

Also fix typo ("progess" -> "progress").  Refactor unit test, and add unit test coverage for log message.
I hand-tested this on a single-part query from sqlcmd, which works fine.  Just now, I tried a multi-part long-running query and you're right.  I'm not getting the behavior I expected.  Thanks for catching this!