Split out violations into separate table

  * Makes `Violation` inherit from `ActiveRecord::Base` and adds associated
    table
  * Adds `has_many :violations` association to `Build`
  * Updates creation of `violations` in `style_guide`'s
  * Adds `violation` factory

EDIT: this PR also renames the column `builds.violations` to `builds.violations_archive` allowing us to migrate the historical violations at a later date while making sure we're not still using this column in production.

https://trello.com/c/OLdRI0mO/336-split-out-violations-into-separate-table
That idea is an interesting one. I feel that I don't ever trust the model validations to be complete so I go to look at the database directly to get the complete picture. I would prefer to leave them off the application in the name of less code.