perf: move assemble status to redis

[anonrig]

Dual writes to memcache and redis while transitioning assemble status to redis

Ref: #68598

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.90%. Comparing base (5cee6c2) to head (888a35d).
Report is 9 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #70344       +/-   ##
===========================================
+ Coverage   50.59%   79.90%   +29.31%     
===========================================
  Files        6473     6503       +30     
  Lines      288640   289975     +1335     
  Branches    49726    49950      +224     
===========================================
+ Hits       146029   231714    +85685     
+ Misses     142199    57848    -84351     
- Partials      412      413        +1     

Files	Coverage Δ
src/sentry/conf/server.py	89.23% <100.00%> (-0.02%)	⬇️
src/sentry/options/defaults.py	100.00% <100.00%> (ø)
src/sentry/tasks/assemble.py	89.45% <100.00%> (+61.53%)	⬆️
src/sentry/testutils/helpers/redis.py	100.00% <100.00%> (+46.15%)	⬆️

... and 2102 files with indirect coverage changes

[markstory]

Logic to read/write values looks good to me once the type issues are sorted.

[asottile-sentry]

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ KeyError: 'Invalid cluster type, expected redis cluster' /api/0/organizations/{organization_slug}/releas... View Issue

_{Did you find this useful? React with a 👍 or 👎}

[getsentry-bot]

PR reverted: c486707