feat(replay): use replay_event instead of querying clickhouse for rage click issues

[JoshFerge]

if the replay event exists, use that instead of querying clickhouse to create a rage click issue.

related:#65291
#65298
getsentry/relay#3035
getsentry/sentry-kafka-schemas#213

[codecov]

Codecov Report

Attention: Patch coverage is 25.00000% with 9 lines in your changes are missing coverage. Please review.

Project coverage is 50.72%. Comparing base (b399327) to head (5f26f13).

❗ Current head 5f26f13 differs from pull request most recent head 8c40a51. Consider uploading reports for the commit 8c40a51 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #65307       +/-   ##
===========================================
- Coverage   83.36%   50.72%   -32.64%     
===========================================
  Files        5271     5243       -28     
  Lines      235726   235016      -710     
  Branches    40794    40692      -102     
===========================================
- Hits       196517   119218    -77299     
- Misses      38990   115575    +76585     
- Partials      219      223        +4     

Files	Coverage Δ
src/sentry/replays/usecases/ingest/dom_index.py	30.18% <25.00%> (-60.26%)	⬇️
...c/sentry/replays/usecases/ingest/issue_creation.py	48.64% <25.00%> (-44.46%)	⬇️

... and 2037 files with indirect coverage changes

[cmanallen]

Was the ClickHouse query removed in a different PR?

[JoshFerge]

Was the ClickHouse query removed in a different PR?

no, the clickhouse query is not removed yet. it will be removed in a future PR, after all kafka messages have replay_event.

[cmanallen]

Please verify this does not double write. Otherwise looks good.

[sentry-io]

Suspect Issues

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

• ‼️ OperationalError: timed out sentry.celery in apply_async View Issue

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