fix(rq): handle new Job.get_status() exception

[fancyweb]

Fixes #7985 again with rq 2.0.0.

rq 2.0.0 has been released about four weeks ago.

Since rq/rq#2039, Job.get_status() doesn't return None but raises InvalidJobOperation when refresh=True (which is the default behavior).

The proposed change is retro-compatible with previous supported versions.

I manually bumped rq latest to 2.0.0 since it's currently untested.

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[fancyweb]

Catching all exceptions looks safer to avoid similar problems in the future.

[fancyweb]

Better be safe since rq itself did not handle the new error well, which means using ddtrace-run currently makes the workers crash in such a scenario (see rq/rq#2154 (comment))