Feature/console debugging

[IAmThePan]

• Have you followed the guidelines in CONTRIBUTING.md?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what your changes do?
• Does your submission pass tests?
• Did you lint your code prior to submission?

I created a window.GHOSTERY object for debugging purposes.

There are 2 ways you can find this information:

1. Open the background.js console from chrome://extensions. Call window.GHOSTERY.getTabInfo() to populate the foundBugs and tabInfo objects. Call window.GHOSTERY.getUserData() to populate the user object.
2. Open the extension, click the menu, and click Help. Click the "Help for Ghostery Browser Extension" text five times (like how you enable developer mode on Android). An "Open Debug Information" link will appear, click on that. A new tab will open at app/templates/debug_information.html. This will run both getTabInfo() and getUserData() to populate the window.GHOSTERY object. It will then output the object in JSON to the page and download the JSON as a file.

Option 1 is meant for to be used by developers wanting debug information as they build the extension. Option 2 is meant for users who run into issues so they can send concise, relevant information to the Ghostery support team.
For Option 2, I don't expect we will both show a JSON web file and download the file; I wanted to showcase the options.

[christophertino]

Relates to #43. This will allow users to debug account events in the console with ghostery.getUserData()