Comment on PR when config is invalid

* Hound users currently receive no feedback when their Ruby, JavaScript,
  and CoffeeScript configuration files are invalid. This commit
  introduces a new feature to address this disconnect:
  When a config file is empty or can't be parsed, Hound will leave
  a comment on your pull request indicating that the config file is
  invalid.
* Validate repo config in `BuildRunner#run`
* Add `RepoConfig#validate` and `RepoConfig#errors`
* Add `GithubApi#add_issue_comment` and `PullRequest#add_comment`
* https://trello.com/c/JLt3FVUb/397-comment-on-the-pr-that-breaks-configuration
Since, we control the setup, and know that there weren't any errors What do you think about avoiding using `expect {}`, and instead doing this:
```ruby
...

config.validate

expect(config.errors.size).to eq 1
```
It's nice to see a distinct execution and verification separate like this.