Removing versioning test since problem is in paper_trail not globalize, as discussed in #285.

This reverts commit 98fdc1a33be965743fcf220d826bb007e321ec6f, reversing
changes made to ae462f8e5eeaf9ac5df9b576ebf3ce68c551b314.
move where_values_hash patch into globalize relation class so we don't
have to monkeypatch activerecord, fixes #288.
skip two failing tests for now, but we need to fix these before we
release 4.0.0.
move create_row_test.rb to test directory.
Added Code Climate Score

https://codeclimate.com/github/globalize/globalize
Merge pull request #293 from BrandonMathis/master

Added Code Climate Score
use FriendlyId pattern for overriding relation method in order to avoid conflict, should solve issue in #288.
return abstract class from relation_class, for compatibility with friendly_id.
give abstract class a name.
Query using Globalize.fallbacks rather than locale only

When fetching a record users might want to grab values from another
locale in case there's no record for the current locale. e.g.
add tests for querying using fallback locales, discussed in #300.
delete and ignore .ruby-version from repo.
add test for find/where through association issue in #303.
use a module (QueryMethods) rather than a class (Relation) so that we can re-use the same methods when patching CollectionAssociation.
Include QueryMethods in delegated subclasses of ActiveRecord::Relation for
translated model. This enables translated query methods on associations, as
discussed in #303.
Check that delegated relation classes are defined before including
QueryMethods from them, to safeguard against changes in ActiveRecord.
super returns class that includes globalize query methods, so we can call with_translations_in_fallbacks.
Merge pull request #305 from globalize/issue_303_find_through_association

Fixes #303.
use different method name for relation class to avoid possible conflicts with other gems.
no more rbx-19mode.