ref(escalating-issues): Delete GroupForecast Table

[jangjodi]

Step 3 of removing the GroupForecast table

See step 2: removing the GroupForecast model here
See step 1: removing the foreign key constraint in the GroupForecast table here

WOR-2966

[wedamija]

lgtm, please make sure that this isn't merged until #47593 is merged + deployed

[codecov]

Codecov Report

Merging #47601 (97af7fa) into master (fe46cf7) will increase coverage by 21.71%.
The diff coverage is n/a.

❗ Current head 97af7fa differs from pull request most recent head 4812db3. Consider uploading reports for the commit 4812db3 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #47601       +/-   ##
===========================================
+ Coverage   59.09%   80.80%   +21.71%     
===========================================
  Files        4728     4764       +36     
  Lines      200505   201167      +662     
  Branches    11605    11607        +2     
===========================================
+ Hits       118483   162557    +44074     
+ Misses      81766    38354    -43412     
  Partials      256      256               

see 1602 files with indirect coverage changes

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/0424_drop_group_forecast_table.py ()

--
-- Raw SQL operation
--

            DROP TABLE "sentry_groupforecast";
            ;

[barkbarkimashark]

You'll need to delete these tests to get tests to pass:
tests/sentry/migrations/test_0417_backfill_groupedmessage_substatus.py
tests/sentry/migrations/test_0420_backfill_groupedmessage_ignored_substatus.py

[wedamija]

That test failure should be unrelated... I'd try just rebasing on latest master

[barkbarkimashark]

That test failure should be unrelated... I'd try just rebasing on latest master

Was referring to this test failure: https://github.com/getsentry/sentry/actions/runs/4747748622/jobs/8433063906