feat(suspect-commits): Remove suspect commit recalculation period (when all-frames is enabled)

[malwilley]

Closes #57438

See ticket for more info, but we are no longer going to run the process_commit_context task when new events come in. To increase accuracy, we want to calculate the suspect commit only at the time the issue was created. Otherwise we might select commits that were made after the issue started.

There is a lot of cleanup that can be done after GA (around removing the debounce cache especially), but this is the first step.

Note: depends on #58307 being merged

[codecov]

Codecov Report

Merging #58415 (8e913c0) into master (3889396) will increase coverage by 2.60%.
Report is 4 commits behind head on master.
The diff coverage is 100.00%.

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

@@            Coverage Diff             @@
##           master   #58415      +/-   ##
==========================================
+ Coverage   76.48%   79.09%   +2.60%     
==========================================
  Files        5140     5144       +4     
  Lines      224551   223980     -571     
  Branches    37843    37715     -128     
==========================================
+ Hits       171755   177149    +5394     
+ Misses      46987    41154    -5833     
+ Partials     5809     5677     -132     

Files	Coverage Δ
src/sentry/tasks/post_process.py	91.06% <100.00%> (+19.89%)	⬆️

... and 723 files with indirect coverage changes

[wedamija]

This seems ok but have we considered the merging case?

[malwilley]

@wedamija we did consider merging, but have decided that merging non-related problems together is something we don't want to try to support since it makes the common case (each issue has one cause) more difficult to get right. If you have ideas on that front I'm all ears!

cc @armenzg