FIX: avoid using Redis keys command since it scans the whole db keys

Keep track of the timestamps at which a give job occurs in a separate
set. This is redundant but useful if you want to provide a way to remove
scheduled jobs without potentially incurring in seriously performance
issues.
Add a migration script to be used to migrate to
the new job timestamps tracking on an existant
resque-scheduler redis db.
Add scheduled_at method

It returns an array of timestamps the selected job is scheduled at
Merge pull request #1 from potomak/master

Find job schedules time
Delete set tracking timestamps on remove_delayed

When removing all occurencies of a given delayed item remove also the
key used to track the timestamps at which the job was scheduled.
Merge branch 'master' of github.com:bugant/resque-scheduler
Remove items from the timestamps set instead of deleting it

Remove items instead of deleting the timestamp set. This prevent to
delete some new jobs added while deleting the old ones.
Remove elements from the timestamps set in next_item_for_timestamp and remove_delayed_job_from_timestamp
Add test to check that after reset no timestamps set is left
Fix failing test where remove_delayed was returning nil, possibly due to a newer Redis version.
Merge the two remove_delayed pipelined blocks.

I can't think why these were separate to begin with. Maybe because of how the replies are returned?
Add enqueue_delayed for enqueing specific delayed jobs immediately
Merge pull request #2 from chewi/master

Add enqueue_delayed for enqueing specific delayed jobs immediately
Make the replies processing more clear
Merge branch 'master' of https://github.com/bvandenbos/resque-scheduler

Conflicts:
	lib/resque_scheduler.rb
Merge pull request #167 from bugant/master

Efficent remove_delayed implementation