Making extensions/chromium/*.js adhere to the style guide

[timvandermeij]

@Snuffleupagus I apologize in advance because this might be hard to review. Most files (especially chrome.tabs.executeScriptInFrame.js) were indented in a different way than in the style guide, so fixing that causes the diff here to be hard to parse. It might be easier to just use the View button for some files and go through the files to see if all is correct.

It would be nice if you could compile the Chrome extension and test it to make sure nothing is broken.

[Rob--W]

No functional changes, +1 from me.

To make reviewing a bit easier, just add ?w=1 to the URL, to ignore whitespace:
https://github.com/mozilla/pdf.js/pull/4426/files?w=1

[brendandahl]

Maybe I missed something on IRC, are we trying to get it so we run jshint with the 'curly' option?

[timvandermeij]

@brendandahl Yes. It's mostly to make the codebase itself adhere to the style guide, but a useful side effect is that we can hopefully enforce the curly option in jshint to make sure the codebase stays in line with the style guide and to avoid unnecessary review comments.