chore(sentry apps): add slos for issue link req

[Christinarlong]

Very similar to the SelectRequester external request SLOs. This module we send out a request to the 3p telling them this user would like to link their Sentry issue to your ext platform.
The failure modes for this module are almost the same for SelectRequester

We can fail in a few ways here:

• Integrator returns some bad error code (400-500) -> halt
• Integrator returns some bad response -> halt
• Some other Unexpected Error -> failure

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #87775      +/-   ##
==========================================
+ Coverage   87.73%   87.79%   +0.06%     
==========================================
  Files        9991     9968      -23     
  Lines      565181   565079     -102     
  Branches    22276    22146     -130     
==========================================
+ Hits       495840   496109     +269     
+ Misses      68919    68569     -350     
+ Partials      422      401      -21     

[cathteng]

nit: maybe make this into a variable and reuse instead of declaring this 3x?

[cathteng]

same thing with recording the halt 🤔

[Christinarlong]

okes to the reusing of the halt reason, though I think it's okay to keep the halt part since, imo, it's a bit easier to trace, that in this flow we recorded a halt for this use case.

[cathteng]

nit: you are already recording the exception as the halt reason, do you also need to add it to extras?

[Christinarlong]

We're add the error_message here to be included in the webhook_context for the integrator, but yes it's redundant for the context manager.