Use sadd? srem? when available to not trigger deprecation warning

Use sadd? srem? when available to not trigger deprecation warning on …

…Redis > 4.2 (#19)

When using redis 4.8+ and still calling sadd/srem - redis spits deprecation warning that these methods soon will return integer instead of boolean.

This change not only puts unnecessary log lines - but also makes gem incompatible with redis 5 as we were checking fact of removing the job.

At some point - we should increase min supported redis version and remove the workaround

Support for sidekiq 6.5

Merge pull request #16 from matic-insurance/allow_sidekiq_6_5

Update sidekiq-group.gemspec

Fix for Sidekiq::Client.push_bulk

MIS-3774: fix for bulk push (#15)

* MIS-3774: fix for bulk push

* MIS-3774: update version

Add methods to track progress

MIS-3774: add progress methods (#14)

* MIS-3774: add progress methods

* MIS-3774: fix specs and rubocop

* MIS-3774: update version

* MIS-3774: update version

* MIS-3774: fix debug logs

Update sidekiq to 6.4.2

0.1.7

Update version (#13)

Fix race condition issue

v0.1.6

update version in Gemfile.lock

Add debug logs

v0.1.5

fix publish (#8)

Update version

v0.1.3

Update version.rb

Update Rakefile

0.1.2

Update Rakefile

Fix release GitHub action

0.1.1

Update publish.yml (#3)