Revert "Upgrade RuboCop to 0.23.0"

This reverts commit 1e3e4200579fd567a53b417f15776c98d1e2650d.

Rubocop has changed their configuration structure which will break existing
config for all of our users. Until we find a strategy to deal with this, we
should not upgrade any higher.
Lock RuboCop to v0.22.0

* Update configuration link to point to the right tag of RuboCop
Update configuration.haml

That ain't YAML. This is YAML.
Extract CommentingPolicy policy object

* Extract `CommentingPolicy` object for logic around permitting
  Hound to comment on a line in a pull request
Add Hound logo to home page

* Add Hound SVGs to home page
* Move line on homepage to the left
* Remove old hound image

https://trello.com/c/U2GJGKlo
Merge pull request #286 from bhardin/patch-1

Update configuration.haml
Clean up Commenter and CommentingPolicy specs

* Remove specs testing logic currently tested in `CommentingPolicy`
  specs from `Commenter`
* Don't stub unused and nonexistent methods in `CommentingPolicy` specs
Rename CommentingPolicy spec to have suffix

Tighten up some lines that dont need to wrap beyond one line.
Post Travis build status to #hound

* Notify on build failure
* Notify on first success after previous failure
Switch to byebug gem for debugging

* `byebug` has a better support for Ruby 2.0 than `debugger`
* `debugger` statement can still be used (with all the familiar commands)
Revert "Use Linguist to determine file language"

* Deploying to Heroku turned out to be huge pain because of libicu.

This reverts commit 4d0ec94830d3ba0cb9c665cf61c8c10a0f2bdd96.
Refactor ModifiedFile to CommitFile

Generalize the name to handle files that may not have been modified, like
`.hound.yml`.
Support exclusion of files from the config

Check file exculsion via Rubocop's `Config#file_to_exclude?` method.