Extended HttpClientProblem's whitelist

To account for when the HttpRequest is put into a logger or sysout'ed
Made a test for fields

Also tested the logging bit.

(real talk: I wrote this test and had to add a few things to the
whitelist in HCP)
Two minor FindBugs things

Default break and making class static
Refactoring Logger Oddities

Extracting methods and regrouping nested if statements
Tentatively able to identify proper uses for getName in Logger

I'm forwarding on the constant value if the getName() is called via
userValues, which should allow me to use the same bug detection logic
Resolves kjlubick/fb-contrib/issues/18

There is a bit of refactoring scattered throughout this.
I updated the message to show what was seen and what is expected, to
help identification of the problem.
The comments on lines 162 and 163 help explain what I do, basically when
we see a call to getName(), we pass the current uservalue forward
(passing the name of the class used to instantiate the logger)
Merge branch 'outgoingChanges'