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
Now that you mention it, it **is** a very Lars thing to do. I'll try to remember that. 
Both Go- and Javascript documentation and examples also always uses `i` and `j` for loops but it's only in Python I see the `x` being used in a list comprehension.