Adding ability to analyze omni.ja - the JS side of b2g

With this tool, you can pull omni.ja off the device, unzip it, and analyze the contents of the JS and manifest files. It will detect things that have been added and things that have been changed. To run it, you would run it with the --generate flag to generate you a reference JSON structure. And then you would run it referencing that JSON file as your verification file with the partner device connected. So, to surmise:
1. Connect a phone running release b2g build you want to test. Run tool with --generate to get reference JSON 
2. Ship reference JSON with this certsuite - might want a reference JSON for each release version
3. When running at partner site with partner phone attached reference the proper reference JSON for the release version and the partner's build will be compared to the release version.
4. An output JSON is generated containing the differences between the partner build and the release build.
5. This output JSON is sent back to Mozilla for analysis
6. Another method, as yet unwritten, should be provided that will take the output JSON and decode the tagged files and diff them against the files in the release b2g build so that the differences can be analyzed.