log output: initial move to DATADUMP

This moves most of the biggest log outputs from DEBUG and INFO to DATADUMP. Turns out, there weren't all that many.

Next I'm reevaluating the log level assigned to each output. Ideally I'm thinking the default log level should be INFO (20) and should give the user a good picture of what their node is doing on the network without being too much or too many to read in realtime.
> Yes but only on the grounds that we're changing the quotes based on the presence or absence of escape sequences.

That's right, Google [suggests](http://google-styleguide.googlecode.com/svn/trunk/pyguide.html?showone=Strings#Strings) doing so, too.

If I had to pick a style for everyone to follow, that would be this: All strings shall be delimited by single quotes, except:
* All doctrings and multi-line strings shall be delimited with double quotes (PEP 257).
* Any string that includes escaping single or double quotes should be written as to minimize the number of escaped quotes. Raw strings can be used towards that purpose.

Schemes that alter between single and double quotes depending on the content are neither easy to grasp/enforce nor convey much information. Syntax should be kept separate from semantics as much as possible. I actually object to using single quotes for dict keys, because it stems from languages that use atoms, such as Erlang, Prolog and Ruby. Python doesn't have such a concept. I have also been on a project where double quotes where used solely for strings that contained formatting characters; apparently they were bash afficionados.