Migrate term modifier sets to sorted sets, counting modifications per user
Merge remote-tracking branch 'upstream/master' into modifier_counts

Conflicts:
	spec/lita/handlers/karma_spec.rb
This spec is failing on Travis, though passing locally.

I think this is the bit of non-deterministic behavior
upgrade_data will write actions for the existing karma values
break upgrade_data into 3 methods for each type of upgrade
All the methods that mutate and/or return terms should now also keep the decay in sync
Migrate vanilla JSON to MultiJson

Strange that it works in the spec, but not in the running app.
Update the documentation to reflect the new sorted set for modified:<term>, forcing a bump to 2.2.0

Including instructions on how to change the process for upgrading the existing data.
Merge branch 'modifier_counts' into karma_decay
Update the documentation to discuss karma decay
Updates for Lita 4.
Add config.link_karma_threshold.
Merge remote-tracking branch 'upstream/master' into modifier_counts

Conflicts:
	lita-karma.gemspec
  lib/lita/handlers/karma.rb
Merge branch 'modifier_counts' into karma_decay

Conflicts:
	README.md
	lib/lita/handlers/karma.rb
Merge pull request #8 from erikogan/modifier_counts

Count term modifications by user
Merge pull request #9 from erikogan/karma_decay

Karma decay
Use Lita 3 style entry point and clean up configuration.
Use helper methods for conciseness.
Move messaging into locale file.
Extract config and data upgrades into separate handlers.