Add format and format-verify tasks to grunt

[NickCrews]

This adds two grunt tasks, format and format-verify. The first reformats files for you, and the second just checks that files are formatted, eg for pre-commit hooks.

The src attribute, where the beautifuer looks for files, is wrong of course, but this is helpful for testing within the chipper repo. I still need to figure out how to make it so you can call this from any repo, since at this point when I do that I get an error because Local Npm module "grunt-jsbeautifier" not found. Do I need to add this to every repo's package.json? Somehow I doubt it, since those look really clean at this point...

This uses the .jsbeautifyrc file from https://github.com/phetsims/phet-info/blob/master/ide/sublime-text/.jsbeautifyrc, so this should follow the PHET conventions.

[NickCrews]

This is a first stab at addressing phetsims/phet-info#150

[pixelzoom]

Assigning to @ariel-phet to prioritize and assign.

[NickCrews]

Updated so you can run format and format-all as grunt tasks from any repo. After testing on a couple repos (twixt and energy-forms-and-changes) there were a couple differences. Indentation, import ordering (that comes from your existing grunt task sortImports though...), newlines were changed. I didn't actually like the end result, but it's palatable. Some tweaking still probably possible.

This also only does .js files, but presumably you may want something for all file types. Possibly unibeautify would be useful?

[pixelzoom]

FYI... Merging this pull request in 6887eb5 introduced a new dependency on js-beautify (in format.js). This broke tasks like grunt lint. Everyone will need to do npm prune and npm update in their local chipper repo. I posted a PSA to the dev-public Slack channel.

This is the kind of breaking change that should probably be announced on the Google Group, but I haven't done that.

[zepumph]

Sorry about that @pixelzoom! I will fix this while we are experimenting, and only add a dependency if we go down this road.

[NickCrews]

Hey, thanks @zepumph for keeping the momentum going! This looks great. I'll add a few comments in phetsims/phet-info#150.

One thing though, is I notice that package-lock.json is not checked into this, or any phet repo. I'm an NPM newbie, but as I understand it package-lock.json should be checked in so that your dependency tree is always exactly reproducible. This possibly deserves its own discussion, but if this is a conscious choice by PHET then ignore me.

[pixelzoom]

It might be worth discussing again, because I don't recall the discussion. But turning off package-lock.json was a conscious decision by PhET. And it's an explicit step in the "Getting Started" sections of the PhET Development Overview:

7. Run npm config set save false so that package-lock.json files are not created.