Add Rubocop to the project

Those of us that were at the sprint in May will remember that Hound CI was brought up because we wanted to try and automate the use of Rubocop. However, we completely forgot to add Rubocop to the project.

Hound does style checking in the PR, but that can be incredibly noisy ~~sometimes~~ a lot of the time. Though we cannot force someone to use Rubocop before opening a PR, having Rubocop in the default project configuration might act as a reminder.

I've linked the Hound and Rubocop configuration files, so you _should_ be able to just run `rubocop` on a file or directory and get the same results that Hound would give you. In practice, the results might be different due to the Gemfile locking onto an older version of Rubocop than what Hound is using.
Whoops, accidentally lost my previous comment here for somehow. Retyping...

I was wondering how does this syntax work -- does Hound really look into `.rubocop.yml` after it reads this?

I've seen the use of `inherit_from` in Rubocop configs, but I read from the Hound site that
> [...] most of the RuboCop configuration, except inheritance, is supported in Hound as well.

So I was under the impression that we need to put everthing in `.hound.yml`, and have `.rubocop.yml` define `inherit_from` to share the Hound config.