Add specs for style guide formatting

These specs cover the formatting section of the style guide.  Some pending specs cover guidelines that are not yet supported in Hound.

- [x] Avoid inline comments.
- [x] Break long lines after 80 characters.
- [x] Delete trailing whitespace.
- [x] Don't include spaces after (, [ or before ], ).
- [x] If you break up a chain of method invocations, keep each method invocation on its own line. Place the . at the end of each line, except the last. Example.
- [x] Use an empty line between methods.
- [x] Use newlines around multi-line blocks.
- [x] Use spaces around operators, after commas, after colons and semicolons, around { and before }.
- [x] Use uppercase for SQL key words and lowercase for SQL identifiers.

Not explicitly tested for:

- [ ] Don't misspell.
- [ ] Don't vertically align tokens on consecutive lines.
- [ ] If you break up an argument list, keep the arguments on their own lines and closing parenthesis on its own line.
- [ ] If you break up a hash, keep the elements on their own lines and closing curly brace on its own line.
- [ ] Indent continued lines two spaces.
- [ ] Indent private methods equal to public methods.
- [ ] Use 2 space indentation (no tabs).
- [ ] Use Unix-style line endings.