Speed: Optimize logging on hot-path

Our scanner currently generates a several log messages for each request made to the target application. This is great for testing purposes, but may be causing unneeded slow downs. Additionally, the scanner logs to the console extensively, which is not needed unless running locally for development purposes.

1. Turn off console logging in production
2. Does turning off logging have a noticable impact on testing speed?
   1. Should we add a verbose variable to turn on debug information?
   2. Can we trim or combine multiple log messages into one?
   3. Is another log mechanism faster?
   4. Are we doing unefficient things on log messages that are not shown by default?
      1. Formatting strings we pass in? This should be done by the log framework instead of caller.