Ruleset updating mechanism to fetch, verify the authenticity of, and apply new ruleset databases

This pull request contains all of the commits I (Zack Mullaly) have made over the course of the Summer of 2014 to build a secure ruleset updating mechanism for my Google Summer of Code 2014 project.
There are still some details (such as a public key) that need to be filled in by whoever now is the primary maintainer of the project, but the feature should be functional once the TODOs are taken care of.
I'd rather parse "development" and "5.0.0" out of the detected version of the extension at runtime, ex: "5.0development.0". Then we don't have to update these two prefs when a new version of the extension is installed.

(IIRC, if you update a pref's value in defaults/preferences/preferences.js, it won't override existing values of the pref in the user's profile.)