feat(github): detecting fatal error for disabling integrations

[chloeho7]

Storing fatal error for disabling Github integrations
Milestone 3 of Notify on Disabled Integration project

[codecov]

Codecov Report

Merging #54286 (e0fe056) into master (215fad6) will increase coverage by 25.54%.
The diff coverage is 69.23%.

❗ Current head e0fe056 differs from pull request most recent head 2e7cdba. Consider uploading reports for the commit 2e7cdba to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #54286       +/-   ##
===========================================
+ Coverage   54.33%   79.87%   +25.54%     
===========================================
  Files        5010     5025       +15     
  Lines      213416   213821      +405     
  Branches    36314    36374       +60     
===========================================
+ Hits       115950   170796    +54846     
+ Misses      94501    37786    -56715     
- Partials     2965     5239     +2274     

Files Changed	Coverage Δ
src/sentry/conf/server.py	91.66% <ø> (ø)
src/sentry/shared_integrations/client/base.py	76.97% <46.66%> (+52.35%)	⬆️
src/sentry/features/__init__.py	100.00% <100.00%> (ø)
src/sentry/integrations/github/client.py	85.53% <100.00%> (+62.09%)	⬆️
src/sentry/integrations/request_buffer.py	95.23% <100.00%> (+72.61%)	⬆️

... and 1785 files with indirect coverage changes

[roggenkemper]

should we be doing a similar check for is_integration_fatal_broken if it is github or is that smth we only want to do for slack?

[ceorourke]

^^ it doesn't seem like we're checking if it's broken before disabling right now.

[chloeho7]

This is within the disable function which is called after buffer.is_integration_broken() is True. We did is_integration_fatal_broken for slack since we wanted to turn on the slack flag but only validated the fatal broken integrations. I'm not sure if we will have the same situation with github but we can see what we get in the logging and then decide?