fix(redis): Use command_queue instead of command_stack if available

[sentrivana]

This commit in redis-py moved away from using the Pipeline's command_stack and is now using _execution_strategy.command_queue instead. We need to adapt to use the new command source if present.

This fixes redis-latest in CI.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.66%. Comparing base (ac7646b) to head (0c318ee).
Report is 2 commits behind head on master.

⚠️ Parser warning

The parser emitted a warning. Please review your JUnit XML file:

Warning while parsing testcase attributes: Limit of string is 1000 chars, for name, we got 2301 at 1:2550 in /__w/sentry-python/sentry-python/.junitxml

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4404      +/-   ##
==========================================
+ Coverage   80.62%   80.66%   +0.04%     
==========================================
  Files         142      142              
  Lines       15961    15966       +5     
  Branches     2726     2726              
==========================================
+ Hits        12868    12879      +11     
+ Misses       2238     2231       -7     
- Partials      855      856       +1     

Files with missing lines	Coverage Δ
sentry_sdk/integrations/redis/_sync_common.py	86.79% <100.00%> (+1.37%)	⬆️
sentry_sdk/integrations/redis/utils.py	92.20% <100.00%> (ø)

... and 3 files with indirect coverage changes

[szokeasaurusrex]

Do we need any tests for this, or will it just get "automatically" tested by the latest redis tests?

noticed a potential problem

[sentrivana]

Do we need any tests for this, or will it just get "automatically" tested by the latest redis tests?

The command_stack version is tested by all tests running redis-py<3.1, and the command_queue version is tested by >=3.1, so this is covered.

[szokeasaurusrex]

🚀