Fixes Bug 1084182 -  ensure Hybrid & Proc2015 do the same thing

Now that Processor2015 has been working for a week in staging, round up all the little nits and differences in the Processed Crash produced by the two processor algorithms.

This covers:
  1) remove unused Skunk Classifiers
  2) set Distributor & Distributor_version to None rather than empty string
  3) set URL, Comments, Email to None rather than empty string
  4) rework TopMostFileRule to reflect new location to get the filename
  5) HybridProcessor sometimes has a list of length one of for TopMostFile and other
times it just has a bare filename.  -- make Processor2015 consistent: never a list
  6) Add new location for a bare offset in signature generation.  the old pDump had module offset and offset in the same variable, while the jDump uses separate variables
  7) Add neglected module to lower case for modules from Windows NT  
  8) Processor2015 using wrong crashing stack frames for signature generation, switch to untruncated stack
  9) rework Skunk Classifier messages to go to Processor Notes rather than the System log
 10) rework the SetWindowsPos Skunk rule to have its own Signature tool
 11) Alter the tests to reflect these changes
"explicit is better than implicit" says the canonical Python style guide.  ```None``` may be the implicit default, but by specifying it, I show that it is my explicit intent to have the value None used if ```Distributor``` is missing from the raw_crash.  I'd say that line is PEP20 compliant. 

As for the second point, no, it is not the intent for any of this code change the value from the empty string to None if the original value was the empty string.

The example that you give at the end is really a mystery to me.  Oh, I understand what it does, but I don't see why use of that idiom would ever be acceptable.  Doesn't such an obscure use of what should be a boolean operator violate the intent behind PEP8 and PEP20?  It's a trick that exploits a relatively unknown idiosyncrasy in the way the boolean operators work in Python.  Coming from the perspective of most other programming languages, the line reads as nonsense.